cc-dev-template 0.1.6 → 0.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-dev-template",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Structured AI-assisted development framework for Claude Code",
   "bin": {
     "cc-dev-template": "./bin/install.js"

package/src/skills/create-agent-skills/SKILL.md

@@ -5,91 +5,47 @@ description: Expert guidance for creating, modifying, and auditing Claude Code s
 
 # Create Agent Skills
 
-Expert guidance for building Claude Code skills correctly. Skills are prompts with progressive disclosure—they teach Claude how to perform specific tasks repeatedly and reliably.
-
-## Why Skills Exist
-
-Skills solve one problem: **context window efficiency through progressive disclosure**.
-
-Without skills, complex workflows require loading thousands of lines of instructions upfront. With skills:
-- **Level 1**: Metadata (~100 words) loads at startup for all skills
-- **Level 2**: SKILL.md body (1,500-2,000 words) loads only when triggered
-- **Level 3**: references/, scripts/, assets/ load only when needed
-
-This means Claude can have access to unlimited specialized knowledge without paying the context cost until actually needed.
-
 ## What To Do Now
 
-Determine what the user wants to accomplish with skills.
-
 <step name="Understand Intent">
-Ask the user what they want to do:
+Ask what the user wants to do with skills.
 
-Use `AskUserQuestion` with these options:
-- **Create a new skill** - Build a skill from scratch through guided conversation
-- **Audit existing skills** - Review all skills for best practices compliance
+Use `AskUserQuestion`:
+- **Create a new skill** - Build a skill through guided conversation
+- **Audit existing skills** - Review skills for best practices compliance
 - **Modify a skill** - Update or improve an existing skill
-- **Something else** - Free-form request for other needs
+- **Something else** - Free-form request
 </step>
 
 <step name="Route to Workflow">
-Based on the user's choice:
+Based on choice, read the appropriate workflow:
 
 | Choice | Action |
 |--------|--------|
-| Create a new skill | Read `references/create.md` |
-| Audit existing skills | Read `references/audit.md` |
-| Modify a skill | Read `references/modify.md` |
-| Something else | Help them find the right workflow |
-
-Reading the workflow file is mandatory—it contains the detailed instructions for that workflow.
+| Create | Read `references/create.md` |
+| Audit | Read `references/audit.md` |
+| Modify | Read `references/modify.md` |
+| Something else | Help find the right approach |
 </step>
 
-## Core Skill Principles (Quick Reference)
-
-Before routing, understand these fundamentals that apply to ALL skill work:
-
-### A Skill IS a Prompt
-SKILL.md is not documentation about the skill—it IS what Claude reads when the skill activates. Write it as instructions TO Claude, using imperative form.
-
-### Description = Discovery
-The frontmatter `description` field determines when Claude triggers the skill. Include:
-- Third-person phrasing: "This skill should be used when..."
-- Specific trigger phrases users would say
-- Max 1024 characters
-
-### Structure Matters
-```
-skill-name/
-├── SKILL.md           # Required: lean router (1,500-2,000 words max)
-├── references/        # Detailed docs loaded as needed
-├── scripts/           # Executable utilities (token-efficient)
-└── assets/            # Files used in output, never read into context
-```
-
-### Writing Style
-- **Imperative form**: "Parse the file", "Validate the input"
-- **Never second person**: Avoid phrases like "should parse" or "can validate" with pronouns
-- **Objective instructional tone**: Facts and directives, not suggestions
-
-For complete principles, each workflow will load `references/principles.md` as needed.
-
-## Skill Locations
+## Essential Knowledge
 
-Skills can exist at two levels:
+**A skill IS a prompt.** When activated, Claude reads SKILL.md. It must contain instructions, not documentation about the skill.
 
-| Level | Path | Scope |
-|-------|------|-------|
-| User | `~/.claude/skills/` | Available in all projects |
-| Project | `.claude/skills/` | Shared with team via git |
+**Progressive disclosure.** SKILL.md should be lean (<150 lines). Heavy content goes in references/. This keeps context efficient.
 
-The audit workflow discovers skills at both levels automatically.
+**The test:** After reading SKILL.md, would Claude know what to DO? If it only knows what the skill is about, it's written wrong.
 
-## Bundled Scripts
+For complete principles, workflows load `references/principles.md` as needed.
 
-This skill includes utility scripts for validation and discovery:
+## Quick Reference
 
-- **`scripts/find-skills.js`** - Discovers all skills at user/project levels
-- **`scripts/validate-skill.js`** - Validates a skill against best practices
+**Skill locations:**
+| Level | Path |
+|-------|------|
+| User | `~/.claude/skills/` |
+| Project | `.claude/skills/` |
 
-Run scripts via: `node ~/.claude/skills/create-agent-skills/scripts/[script-name].js`
+**Bundled scripts:**
+- `scripts/find-skills.js` - Discover all installed skills
+- `scripts/validate-skill.js` - Validate a skill's structure