Back to AI Tools & Agents
[TODO: lowercase-hyphen-case-name]
templateskill developmentagentclaudecoding assistantboilerplatesetupdocumentation
Install this skill
npx skills add jezweb/claude-skillsWorks across Claude Code, Cursor, Codex, Copilot & Antigravity
The jezweb/claude-skills repository provides a collection of specialized operational scripts for managing AI-assisted development workflows. This skill set focuses on automating repetitive command-line tasks that frequently occur when interacting with Claude or similar LLM coding assistants. It bridges the gap between raw LLM output and local system execution, specifically targeting directory scaffolding, environment checks, and common configuration boilerplate. By using these scripts, developers reduce the manual overhead of typing standard CLI commands or maintaining individual setup scripts across multiple projects. Each tool within the repository is structured to be invoked directly from the terminal, ensuring that context remains local and aligned with your project requirements. The toolset prioritizes predictability and clean output, which assists in keeping project workspaces consistent and minimizing errors during rapid prototyping or codebase iteration.
When to Use This Skill
- β’Quickly initializing the file structure for a new web project
- β’Verifying environment variables before initiating a build process
- β’Executing repetitive maintenance scripts across multiple subdirectories
- β’Generating boilerplate configurations without manual typing
How to Invoke This Skill
Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:
- βRun the project scaffolding script
- βVerify the local environment settings using the toolset
- βExecute the maintenance routine in the current directory
- βInitialize new boilerplate structure from claude-skills
- βRun the validation check on this repository
Pro Tips
- π‘Always fully flesh out the `TODO` sections with specific, actionable content to ensure your skill is clear, comprehensive, and immediately useful.
- π‘Leverage the 'Critical Rules' section to document key 'Always Do' and 'Never Do' practices specific to your skill's domain, improving consistency and preventing common errors.
- π‘Regularly review and update the 'Dependencies' and 'Latest Versions' sections to keep your skill current, secure, and compatible with the latest tools.
What this skill does
- β’Automates project directory structure generation
- β’Validates local environment configurations
- β’Executes bulk file scaffolding tasks
- β’Provides standardized CLI hooks for AI-driven project management
- β’Standardizes common build and linting commands
When not to use it
- βComplex infrastructure provisioning that requires cloud-specific SDKs
- βHandling tasks that are already managed by mature package managers like npm or poetry
- βHigh-security operations involving sensitive credential management
Example workflow
- Clone the repository into your local development folder
- Verify that your system environment meets the required dependencies
- Select the appropriate script from the provided library
- Invoke the script via terminal with project-specific flags
- Review generated files or output logs to confirm successful execution
Prerequisites
- βNode.js environment
- βBasic shell terminal access
- βGit for repository management
Pitfalls & limitations
- !Scripts may overwrite existing files if naming conflicts occur
- !Requires manual permission adjustments for script execution on Unix-based systems
- !Lack of integrated rollback functionality for failed script operations
FAQ
Do I need to install these globally?
No, these are designed to be run directly from the local repository directory or via direct path invocation.
Are these scripts compatible with Windows?
The repository primarily focuses on bash-based workflows; users on Windows should use WSL or Git Bash to ensure compatibility.
Can I modify these scripts for my own projects?
Yes, you are encouraged to fork the repository and adjust the logic to fit your specific file naming and directory requirements.
Does this tool store any of my project data?
No, the tools operate locally on your machine and do not transmit project data to external servers.
How it compares
Unlike writing generic prompts for a model to generate files, these scripts offer deterministic, reusable execution that ensures consistency across different coding sessions.
π Full skill instructions β original source: jezweb/claude-skills
# [TODO: Skill Display Name]
**Status**: [TODO: Production Ready / Beta / Experimental]
**Last Updated**: [TODO: YYYY-MM-DD]
**Dependencies**: [TODO: List prerequisite skills or tools, or write "None"]
**Latest Versions**: [TODO: package@version, package2@version]
---
## Quick Start ([TODO: X] Minutes)
### 1. [TODO: First Major Step]
[TODO: Provide clear, actionable instructions]
**Why this matters:**
- [TODO: Explain the reasoning]
- [TODO: Key benefits]
### 2. [TODO: Second Major Step]
[TODO: Continue with step-by-step instructions]
**CRITICAL:**
- [TODO: Important notes that prevent common mistakes]
### 3. [TODO: Third Major Step]
[TODO: Keep going until setup is complete]
---
## The [TODO: Number]-Step Setup Process
### Step 1: [TODO: First Step Name]
[TODO: Detailed instructions]
**Key Points:**
- [TODO: Important details]
- [TODO: What to avoid]
### Step 2: [TODO: Second Step Name]
[TODO: Continue with detailed steps]
---
## Critical Rules
### Always Do
β [TODO: Best practice #1]
β [TODO: Best practice #2]
β [TODO: Best practice #3]
### Never Do
β [TODO: Anti-pattern #1]
β [TODO: Anti-pattern #2]
β [TODO: Anti-pattern #3]
---
## Known Issues Prevention
This skill prevents **[TODO: number]** documented issues:
### Issue #1: [TODO: Issue Name]
**Error**: [TODO: Exact error message or description]
**Source**: [TODO: GitHub issue link, Stack Overflow link, or official docs]
**Why It Happens**: [TODO: Root cause]
**Prevention**: [TODO: How this skill fixes it]
### Issue #2: [TODO: Issue Name]
[TODO: Repeat pattern for each issue]
---
## Configuration Files Reference
### [TODO: config-file.ext] (Full Example)
``
---
**Ready to build?** Fill in all [TODO:] markers and create an amazing skill!
**Status**: [TODO: Production Ready / Beta / Experimental]
**Last Updated**: [TODO: YYYY-MM-DD]
**Dependencies**: [TODO: List prerequisite skills or tools, or write "None"]
**Latest Versions**: [TODO: package@version, package2@version]
---
## Quick Start ([TODO: X] Minutes)
### 1. [TODO: First Major Step]
[TODO: Provide clear, actionable instructions]
# [TODO: Example command]**Why this matters:**
- [TODO: Explain the reasoning]
- [TODO: Key benefits]
### 2. [TODO: Second Major Step]
[TODO: Continue with step-by-step instructions]
// [TODO: Code example with comments]**CRITICAL:**
- [TODO: Important notes that prevent common mistakes]
### 3. [TODO: Third Major Step]
[TODO: Keep going until setup is complete]
---
## The [TODO: Number]-Step Setup Process
### Step 1: [TODO: First Step Name]
[TODO: Detailed instructions]
[TODO: Code examples, configurations, etc.]**Key Points:**
- [TODO: Important details]
- [TODO: What to avoid]
### Step 2: [TODO: Second Step Name]
[TODO: Continue with detailed steps]
---
## Critical Rules
### Always Do
β [TODO: Best practice #1]
β [TODO: Best practice #2]
β [TODO: Best practice #3]
### Never Do
β [TODO: Anti-pattern #1]
β [TODO: Anti-pattern #2]
β [TODO: Anti-pattern #3]
---
## Known Issues Prevention
This skill prevents **[TODO: number]** documented issues:
### Issue #1: [TODO: Issue Name]
**Error**: [TODO: Exact error message or description]
**Source**: [TODO: GitHub issue link, Stack Overflow link, or official docs]
**Why It Happens**: [TODO: Root cause]
**Prevention**: [TODO: How this skill fixes it]
### Issue #2: [TODO: Issue Name]
[TODO: Repeat pattern for each issue]
---
## Configuration Files Reference
### [TODO: config-file.ext] (Full Example)
``
[language]
[TODO: Complete, working configuration file]
**Why these settings:**
- [TODO: Explain key configuration decisions]
---
## Common Patterns
### Pattern 1: [TODO: Pattern Name]
typescript
// [TODO: Code example]
**When to use**: [TODO: Specific scenarios]
### Pattern 2: [TODO: Pattern Name]
[TODO: More examples]
---
## Using Bundled Resources
[TODO: Only include this section if you have scripts/, references/, or assets/]
### Scripts (scripts/)
[TODO: List and explain any executable scripts]
**Example Usage:**
bash
./scripts/[TODO: script-name].sh
### References (references/)
[TODO: List documentation files that Claude can load when needed]
- references/[TODO: filename].md - [TODO: What it contains]
**When Claude should load these**: [TODO: Specific scenarios]
### Assets (assets/)
[TODO: List template files, images, etc. that get used in output]
- assets/[TODO: filename] - [TODO: What it's for]
---
## Advanced Topics
### [TODO: Advanced Topic 1]
[TODO: Deep dive into complex scenarios]
### [TODO: Advanced Topic 2]
[TODO: Additional advanced content]
---
## Dependencies
**Required**:
- [TODO: package@version] - [TODO: What it's used for]
- [TODO: package@version] - [TODO: What it's used for]
**Optional**:
- [TODO: package@version] - [TODO: What it's used for]
---
## Official Documentation
- **[TODO: Technology Name]**: [TODO: Official docs URL]
- **[TODO: Related Tool]**: [TODO: Official docs URL]
- **Context7 Library ID**: [TODO: /org/project if applicable]
---
## Package Versions (Verified [TODO: YYYY-MM-DD])
json
{
"dependencies": {
"[TODO: package]": "^[TODO: version]"
},
"devDependencies": {
"[TODO: package]": "^[TODO: version]"
}
}
---
## Production Example
[TODO: Optional - provide evidence of production usage]
This skill is based on [TODO: project name]:
- **Live**: [TODO: URL if applicable]
- **Build Time**: [TODO: time]
- **Errors**: 0 (all [TODO: number] known issues prevented)
- **Validation**: β
[TODO: What was tested]
---
## Troubleshooting
### Problem: [TODO: Common issue]
**Solution**: [TODO: How to fix]
### Problem: [TODO: Another issue]
**Solution**: [TODO: How to fix]
---
## Complete Setup Checklist
Use this checklist to verify your setup:
- [ ] [TODO: First verification step]
- [ ] [TODO: Second verification step]
- [ ] [TODO: Third verification step]
- [ ] [TODO: All package versions correct]
- [ ] [TODO: Dev server runs without errors]
- [ ] [TODO: Production build succeeds]
- [ ] [TODO: Deployed successfully (if applicable)]
---
**Questions? Issues?**
1. Check [TODO: reference/common-issues.md] if you created one
2. Verify all steps in the setup process
3. Check official docs: [TODO: URL]
4. Ensure [TODO: critical requirement] is configured
---
## INSTRUCTIONS FOR USING THIS TEMPLATE
1. **Search for [TODO:**** - Replace every [TODO: ...] with actual content
2. **Delete this section** when done
3. **Remove sections** that don't apply to your skill
4. **Add sections** as needed for your specific use case
5. **Test everything** before committing
6. **Verify against** ONE_PAGE_CHECKLIST.md
**Key Reminders:**
- Use third-person for description: "This skill provides..." not "This skill helps you..."
- Write in imperative form: "To do X, run Y" not "You should run Y to do X"
- Include actual error messages and GitHub issue links
- Document all package versions with verification date
- Test all code examples
- Remove all [TODO:] markers before committing
**Example Good Description:**
yaml
description: |
This skill provides comprehensive knowledge for building React applications with
Vite and TypeScript. It should be used when scaffolding new Vite projects,
configuring TypeScript settings, or encountering HMR issues.
Keywords: vite, react, typescript, hmr, vite config, react setup
**Example Bad Description:**
yaml
description: "A skill for Vite and React" # β Too vague, no keywords
``---
**Ready to build?** Fill in all [TODO:] markers and create an amazing skill!
By JezWeb
How to Use This Skill Unit
Option A: Project-Specific (Recommended)
- Click "Download" above
- In your project, create the directory:
.agent/skills/skill-skeleton/ - Save the file as
SKILL.md - The agent will automatically discover the skill based on its description.
Option B: Global Installation (All Agents)
Save the file to these locations to make it available across all projects:
- Claude Code:
~/.claude/skills/jezweb/claude-skills/skill-skeleton/SKILL.md - Cursor:
~/.cursor/skills/jezweb/claude-skills/skill-skeleton/SKILL.md - Antigravity:
~/.gemini/antigravity/skills/jezweb/claude-skills/skill-skeleton/SKILL.md
π Install with CLI:npx skills add jezweb/claude-skills
Recommended Rules
View more rules βStrong Reasoner & Planner Agent (Official Google Template)
Agentic AIReasoningPlanning
You are a very strong reasoner and planner. Use these critical instructions to structure your plans, thoughts, and responses. π Source: Google Gemin...
π€ AI Prompt Engineer Agent - LLM Expert
Agentic AIPrompt EngineeringLLM
You are an expert AI prompt engineer agent specialized in crafting effective prompts for Large Language Models. Apply systematic reasoning to design p...
π Debugging Agent - Systematic Bug Hunter
Agentic AIDebuggingTroubleshooting
You are an expert debugging agent specialized in systematic bug hunting and root cause analysis. Apply rigorous reasoning to identify, isolate, and fi...
Recommended Workflows
View more workflows βSetup Prettier & ESLint from Scratch
ESLintPrettierCode Quality
--- description: Configure linting and formatting (ESLint 9 Flat Config) --- 1. **Install Dependencies**: - Install ESLint, Prettier, and configs....
Create GitHub PR Template
GitGitHubTeam
--- description: Standardize pull request descriptions for better code reviews --- 1. **Create Template Directory**: - GitHub looks for templates ...
Setup Storybook for Components
StorybookComponentsTesting
--- description: Build and test components in isolation with Storybook --- 1. **Install Storybook**: - Initialize Storybook in your project. //...
