@macpaw/cctk 1.0.0-beta.1

package/templates/claude/commands/registry.json

@@ -0,0 +1,313 @@
+{
+  "name": "commands",
+  "version": "1.0.0",
+  "items": [
+    {
+      "name": "ask",
+      "title": "Ask",
+      "description": "Answer technical and architectural questions.",
+      "files": ["commands/ask.md"],
+      "dependencies": {
+        "commands": ["scout"]
+      }
+    },
+    {
+      "name": "bootstrap",
+      "title": "Bootstrap",
+      "description": "Bootstrap a new project step by step",
+      "files": ["commands/bootstrap.md", "commands/bootstrap/"],
+      "dependencies": {
+        "agents": ["git-manager", "researcher", "planner", "ui-ux-designer", "tester", "debugger", "code-reviewer", "docs-manager", "project-manager"],
+        "skills": ["chrome-devtools", "media-processing"],
+        "commands": ["plan:parallel"]
+      }
+    },
+    {
+      "name": "brainstorm",
+      "title": "Brainstorm",
+      "description": "Brainstorm a feature",
+      "files": ["commands/brainstorm.md"],
+      "dependencies": {
+        "agents": ["planner", "docs-manager"],
+        "skills": ["docs-seeker", "sequential-thinking", "planning"],
+        "commands": ["plan:fast", "plan:hard", "scout:ext", "scout"]
+      },
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "Repomix",
+            "type": "npm",
+            "command": "repomix",
+            "install": "npm install -g repomix"
+          },
+          {
+            "name": "PostgreSQL Client",
+            "type": "brew",
+            "command": "psql",
+            "install": "brew install libpq"
+          }
+        ]
+      }
+    },
+    {
+      "name": "code",
+      "title": "Code",
+      "description": "Start coding & testing an existing plan",
+      "files": ["commands/code.md", "commands/code/"],
+      "dependencies": {
+        "agents": ["ui-ux-designer", "tester", "debugger", "code-reviewer", "project-manager", "docs-manager", "git-manager"],
+        "skills": ["media-processing"],
+        "commands": ["preview", "plan:archive"]
+      }
+    },
+    {
+      "name": "coding-level",
+      "title": "Coding Level",
+      "description": "Enable or disable coding level guidelines for expert-level output.",
+      "files": ["commands/coding-level.md"],
+      "dependencies": {}
+    },
+    {
+      "name": "content",
+      "title": "Content",
+      "description": "Content optimization and copywriting commands",
+      "files": ["commands/content/"],
+      "dependencies": {
+        "commands": ["scout:ext", "scout"]
+      }
+    },
+    {
+      "name": "cook",
+      "title": "Cook",
+      "description": "Implement a feature [step by step]",
+      "files": ["commands/cook.md", "commands/cook/"],
+      "dependencies": {
+        "agents": ["researcher", "planner", "ui-ux-designer", "tester", "debugger", "code-reviewer", "docs-manager", "project-manager", "git-manager"],
+        "skills": ["media-processing"],
+        "commands": ["scout:ext", "scout", "code", "plan", "plan:fast", "plan:parallel", "git:cm"]
+      }
+    },
+    {
+      "name": "debug",
+      "title": "Debug",
+      "description": "Debugging technical issues and providing solutions.",
+      "files": ["commands/debug.md"],
+      "dependencies": {
+        "agents": ["debugger"]
+      }
+    },
+    {
+      "name": "docs",
+      "title": "Docs",
+      "description": "Documentation management commands",
+      "files": ["commands/docs/"],
+      "dependencies": {
+        "agents": ["docs-manager"],
+        "scripts": ["validate-docs"]
+      }
+    },
+    {
+      "name": "fix",
+      "title": "Fix",
+      "description": "Analyze and fix issues [INTELLIGENT ROUTING]",
+      "files": ["commands/fix.md", "commands/fix/"],
+      "dependencies": {
+        "agents": ["debugger", "tester", "researcher", "planner", "git-manager", "ui-ux-designer", "project-manager", "fullstack-developer", "code-reviewer", "docs-manager"],
+        "skills": ["debugging", "problem-solving", "sequential-thinking", "media-processing", "chrome-devtools"],
+        "commands": ["code", "scout:ext", "plan:parallel"]
+      },
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "GitHub CLI",
+            "type": "brew",
+            "command": "gh",
+            "install": "brew install gh"
+          }
+        ]
+      }
+    },
+    {
+      "name": "git",
+      "title": "Git",
+      "description": "Git workflow commands (commit, push, PR, merge)",
+      "files": ["commands/git/"],
+      "dependencies": {
+        "agents": ["git-manager"]
+      },
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "GitHub CLI",
+            "type": "brew",
+            "command": "gh",
+            "install": "brew install gh"
+          }
+        ]
+      }
+    },
+    {
+      "name": "journal",
+      "title": "Journal",
+      "description": "Write some journal entries.",
+      "files": ["commands/journal.md"],
+      "dependencies": {}
+    },
+    {
+      "name": "kanban",
+      "title": "Kanban",
+      "description": "AI agent orchestration board (Coming Soon)",
+      "files": ["commands/kanban.md"],
+      "dependencies": {
+        "skills": ["plans-kanban"]
+      }
+    },
+    {
+      "name": "plan",
+      "title": "Plan",
+      "description": "Intelligent plan creation with prompt enhancement",
+      "files": ["commands/plan.md", "commands/plan/"],
+      "dependencies": {
+        "skills": ["planning"],
+        "scripts": ["plan-manager"],
+        "commands": ["scout", "plan:validate", "journal", "git:cm", "git:cp", "scout:ext"]
+      }
+    },
+    {
+      "name": "preview",
+      "title": "Preview",
+      "description": "Path to markdown file, plan directory, or plans collection",
+      "files": ["commands/preview.md"],
+      "dependencies": {
+        "skills": ["markdown-novel-viewer"]
+      }
+    },
+    {
+      "name": "review",
+      "title": "Review",
+      "description": "Code review and codebase analysis commands",
+      "files": ["commands/review/"],
+      "dependencies": {
+        "agents": ["code-reviewer", "git-manager"],
+        "commands": ["scout:ext", "scout", "fix:parallel"]
+      }
+    },
+    {
+      "name": "scout",
+      "title": "Scout",
+      "description": "Scout given directories to respond to the user's requests",
+      "files": ["commands/scout.md", "commands/scout/"],
+      "dependencies": {},
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "Gemini CLI",
+            "type": "npm",
+            "command": "gemini",
+            "install": "npm install -g @google/gemini-cli",
+            "optional": true
+          },
+          {
+            "name": "OpenCode CLI",
+            "type": "npm",
+            "command": "opencode",
+            "install": "npm install -g opencode",
+            "optional": true
+          }
+        ]
+      }
+    },
+    {
+      "name": "scout:ext",
+      "title": "Scout: External",
+      "description": "Scout given directories to respond to the user's requests",
+      "files": ["commands/scout/"],
+      "dependencies": {},
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "Gemini CLI",
+            "type": "npm",
+            "command": "gemini",
+            "install": "npm install -g @google/gemini-cli",
+            "optional": true
+          },
+          {
+            "name": "OpenCode CLI",
+            "type": "npm",
+            "command": "opencode",
+            "install": "npm install -g opencode",
+            "optional": true
+          }
+        ]
+      }
+    },
+    {
+      "name": "skill",
+      "title": "Skill",
+      "description": "Skill management commands (add, create, optimize)",
+      "files": ["commands/skill/"],
+      "dependencies": {
+        "skills": ["skill-creator", "claude-code", "docs-seeker", "sequential-thinking", "problem-solving", "planning"]
+      },
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "Repomix",
+            "type": "npm",
+            "command": "repomix",
+            "install": "npm install -g repomix"
+          }
+        ]
+      }
+    },
+    {
+      "name": "test",
+      "title": "Test",
+      "description": "Run tests locally and analyze the summary report.",
+      "files": ["commands/test.md", "commands/test/"],
+      "dependencies": {
+        "agents": ["tester"],
+        "skills": ["chrome-devtools", "planning"],
+        "commands": ["preview"]
+      }
+    },
+    {
+      "name": "use-mcp",
+      "title": "Use MCP",
+      "description": "Utilize tools of Model Context Protocol (MCP) servers",
+      "files": ["commands/use-mcp.md"],
+      "dependencies": {
+        "agents": ["mcp-manager"],
+        "skills": ["mcp-management", "mcp-builder"]
+      },
+      "meta": {
+        "externalDeps": [
+          {
+            "name": "Gemini CLI",
+            "type": "npm",
+            "command": "gemini",
+            "install": "npm install -g @google/gemini-cli",
+            "optional": true
+          }
+        ]
+      }
+    },
+    {
+      "name": "watzup",
+      "title": "Watzup",
+      "description": "Review recent changes and wrap up the work",
+      "files": ["commands/watzup.md"],
+      "dependencies": {}
+    },
+    {
+      "name": "worktree",
+      "title": "Worktree",
+      "description": "Create isolated git worktree for parallel development",
+      "files": ["commands/worktree.md"],
+      "dependencies": {
+        "scripts": ["worktree"]
+      }
+    }
+  ]
+}

package/templates/claude/commands/review/codebase/parallel.md

@@ -0,0 +1,122 @@
+---
+description: ⚡⚡⚡ Ultrathink edge cases, then parallel verify with code-reviewers
+argument-hint: [scope-or-prompt]
+---
+
+**Ultrathink** to exhaustively list ALL potential edge cases, then dispatch parallel `code-reviewer` agents to verify: <scope>$ARGUMENTS</scope>
+
+**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
+
+## Workflow
+
+### 1. Ultrathink Edge Cases
+
+Main agent deeply analyzes the scope to LIST all potential edge cases FIRST:
+- Read `codebase-summary.md` for context
+- Use `/scout:ext` to find relevant files
+- **Think exhaustively** about what could go wrong:
+  - Null/undefined scenarios
+  - Boundary conditions (off-by-one, empty, max values)
+  - Error handling gaps
+  - Race conditions, async edge cases
+  - Input validation holes
+  - Security vulnerabilities
+  - Resource leaks
+  - Untested code paths
+
+**Output format:**
+```markdown
+## Edge Cases Identified
+
+### Category: [scope-area]
+1. [edge case description] → files: [file1, file2]
+2. [edge case description] → files: [file3]
+
+### Category: [another-area]
+1. [edge case description] → files: [file4, file5]
+```
+
+### 2. Categorize & Assign
+
+Group edge cases by similar scope for parallel verification:
+- Each category → one `code-reviewer` agent
+- Max 6 categories (merge small ones)
+- Each reviewer gets specific edge cases to VERIFY, not discover
+
+### 3. Parallel Verification
+
+Launch N `code-reviewer` subagents simultaneously:
+- Pass: category name, list of edge cases, relevant files
+- Task: **VERIFY** if each edge case is properly handled in code
+- Report: which edge cases are handled vs unhandled
+
+**Reviewer instruction:**
+```
+Verify these specific edge cases in the given files:
+[list of edge cases]
+
+For each, report:
+- ✅ Handled: [how it's handled]
+- ❌ Unhandled: [what's missing]
+- ⚠️ Partial: [what needs improvement]
+```
+
+### 4. Aggregate Results
+
+Collect all verification reports:
+```markdown
+## Edge Case Verification Report
+
+### Summary
+- Total edge cases: X
+- Handled: Y ✅
+- Unhandled: Z ❌
+- Partial: W ⚠️
+
+### Unhandled Edge Cases (Need Fix)
+| # | Edge Case | File | Status |
+|---|-----------|------|--------|
+| 1 | ...       | ...  | ❌     |
+
+### Partial Handling (Need Review)
+| # | Edge Case | File | Issue |
+|---|-----------|------|-------|
+| 1 | ...       | ...  | ...   |
+```
+
+### 5. Auto-Fix Pipeline
+
+**IF** unhandled/partial edge cases found:
+- Ask: "Found N unhandled edge cases. Fix with /fix:parallel? [Y/n]"
+- **IF yes:** Trigger `/fix:parallel` with unhandled list
+
+### 6. Final Report
+
+- Summary of verification
+- Ask: "Commit? [Y/n]" → use `git-manager`
+
+## Example
+
+```
+User: /review:codebase:parallel auth module
+
+1. Ultrathink → Lists 12 edge cases for auth:
+   - Empty password submission
+   - Token expiry during request
+   - Concurrent login attempts
+   - Invalid refresh token
+   ...
+
+2. Categorize → 3 groups:
+   - Login flow (4 cases)
+   - Token handling (5 cases)
+   - Session management (3 cases)
+
+3. Parallel → 3 code-reviewers verify simultaneously
+
+4. Aggregate → 8 handled, 3 unhandled, 1 partial
+
+5. Fix → User approves → /fix:parallel
+
+6. Final → Commit changes
+```

package/templates/claude/commands/review/codebase.md

@@ -0,0 +1,47 @@
+---
+description: ⚡⚡⚡ Scan & analyze the codebase.
+argument-hint: [tasks-or-prompt]
+---
+
+Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+## Workflow:
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use 2 `researcher` subagents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+
+### Code Review
+
+* After finishing, use multiple `code-reviewer` subagents in parallel to review code. 
+* If there are any issues, duplicate code, or security vulnerabilities, ask main agent to improve the code and repeat the "Testing" process until all tests pass. 
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Plan
+* Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an improvement plan following the progressive disclosure structure:
+  - Create a directory using naming pattern from `## Naming` section.
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+
+**REMEMBER**:
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.

package/templates/claude/commands/scout/ext.md

@@ -0,0 +1,35 @@
+---
+description: ⚡ Use external agentic tools to scout given directories
+argument-hint: [user-prompt] [scale]
+---
+
+## Purpose
+
+Utilize external agentic tools to scout given directories or explore the codebase for files needed to complete the task using a fast, token efficient agent.
+
+## Variables
+
+USER_PROMPT: $1
+SCALE: $2 (defaults to 3)
+RELEVANT_FILE_OUTPUT_DIR: Use `Report:` from `## Naming` section
+
+## Workflow:
+- Write a prompt for 'SCALE' number of agents to the `Task` tool that will immediately call the `Bash` tool to run these commands to kick off your agents to conduct the search:
+  - `gemini -p "[prompt]" --model gemini-2.5-flash-preview-09-2025` (if count <= 3)
+  - `opencode run "[prompt]" --model opencode/grok-code` (if count > 3 and count < 6)
+  - if count >= 6, spawn `Explore` subagents to search the codebase in parallel
+
+**Why use external agentic tools?**
+- External agentic tools are faster and more efficient when using LLMs with large context windows (1M+ tokens).
+
+**How to prompt the agents:**
+- If `gemini` or `opencode` is not available, ask the user if they want to install it:
+  - If **yes**, install it (if there are permission issues, instruct the user to install it manually, including authentication steps)
+  - If **no**, use the default `Explore` subagents.
+- IMPORTANT: Kick these agents off in parallel using the `Task` tool, analyze and divide folders for each agent to scout intelligently and quickly.
+- IMPORTANT: These agents are calling OTHER agentic coding tools to search the codebase. DO NOT call any search tools yourself.
+- IMPORTANT: That means with the `Task` tool, you'll immediately call the Bash tool to run the respective agentic coding tool (gemini, opencode, claude, etc.)
+- IMPORTANT: Instruct the agents to quickly search the codebase for files needed to complete the task. This isn't about a full blown search, just a quick search to find the files needed to complete the task.
+- Instruct the subagent to use a timeout of 3 minutes for each agent's bash call. Skip any agents that don't return within the timeout, don't restart them.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.

package/templates/claude/commands/scout.md

@@ -0,0 +1,28 @@
+---
+description: ⚡⚡ Scout given directories to respond to the user's requests
+argument-hint: [user-prompt] [scale]
+---
+
+## Purpose
+
+Search the codebase for files needed to complete the task using a fast, token efficient agent.
+
+## Variables
+
+USER_PROMPT: $1
+SCALE: $2 (defaults to 3)
+REPORT_OUTPUT_DIR: Use `Report:` from `## Naming` section
+
+## Workflow:
+
+- Write a prompt for 'SCALE' number of agents to the `Task` tool that will immediately call the `Bash` tool to run these commands to kick off your agents to conduct the search: spawn many `Explore` subagents to search the codebase in parallel based on the user's prompt.
+
+**How to prompt the agents:**
+- IMPORTANT: Kick these agents off in parallel using the `Task` tool, analyze and divide folders for each agent to scout intelligently and quickly.
+- IMPORTANT: Instruct the agents to quickly search the codebase for files needed to complete the task. This isn't about a full blown search, just a quick search to find the files needed to complete the task.
+- Instruct the subagent to use a timeout of 3 minutes for each agent's bash call. Skip any agents that don't return within the timeout, don't restart them.
+
+**How to write reports:**
+
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.

package/templates/claude/commands/skill/add.md

@@ -0,0 +1,36 @@
+---
+description: Add new reference files or scripts to a skill
+argument-hint: [skill-name] [reference-or-script-prompt]
+---
+
+Think harder.
+Use `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+
+## Arguments
+$1: skill name (required, default: "")
+$2: reference or script prompt (required, default: "")
+If $1 or $2 is not provided, ask the user to provide it.
+
+## Your mission
+Add new reference files or scripts to a skill at `.claude/skills/$1` directory.
+
+## Requirements
+<reference-or-script-prompt>
+$2
+</reference-or-script-prompt>
+
+## Rules of Skill Creation:
+Base on the requirements:
+- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
+- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
+- If you're given nothing, use `AskUserQuestion` tool for clarifications and `researcher` subagent to research about the topic.
+- If you're given an URL, it's documentation page, use `Explore` subagent to explore every internal link and report back to main agent, don't skip any link.
+- If you receive a lot of URLs, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.
+- If you receive a lot of files, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.
+- If you're given a Github URL, use [`repomix`](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple `Explore` subagents to explore it in parallel, then report back to main agent.
+
+**IMPORTANT:**
+- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches Claude how to perform a specific development task, not what a tool does.
+- Claude Code can activate multiple skills automatically to achieve the user's request.

package/templates/claude/commands/skill/create.md

@@ -0,0 +1,29 @@
+---
+description: Create a new agent skill
+argument-hint: [prompt-or-llms-or-github-url]
+---
+
+Ultrathink.
+Use `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+
+## Your mission
+Create a new skill in `.claude/skills/` directory.
+
+## Requirements
+<user-prompt>$ARGUMENTS</user-prompt>
+
+## Rules of Skill Creation:
+Base on the requirements:
+- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
+- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
+- If you're given nothing, use `AskUserQuestion` tool for clarifications and `researcher` subagent to research about the topic.
+- If you're given an URL, it's documentation page, use `Explore` subagent to explore every internal link and report back to main agent, don't skip any link.
+- If you receive a lot of URLs, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.
+- If you receive a lot of files, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.
+- If you're given a Github URL, use [`repomix`](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple `Explore` subagents to explore it in parallel, then report back to main agent.
+
+**IMPORTANT:**
+- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches Claude how to perform a specific development task, not what a tool does.
+- Claude Code can activate multiple skills automatically to achieve the user's request.

package/templates/claude/commands/skill/fix-logs.md

@@ -0,0 +1,22 @@
+---
+description: Fix the agent skill based on `logs.txt` file.
+argument-hint: [prompt-or-path-to-skill]
+---
+
+Think harder.
+Use `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+
+## Your mission
+Fix the agent skill based on the current `logs.txt` file (in the project root directory).
+
+## Requirements
+<user-prompt>$ARGUMENTS</user-prompt>
+
+## Rules of Skill Fixing:
+Base on the requirements:
+- If you're given nothing, use `AskUserQuestion` tool for clarifications and `researcher` subagent to research about the topic.
+- If you're given an URL, it's documentation page, use `Explorer` subagent to explore every internal link and report back to main agent, don't skip any link.
+- If you receive a lot of URLs, use multiple `Explorer` subagents to explore them in parallel, then report back to main agent.
+- If you receive a lot of files, use multiple `Explorer` subagents to explore them in parallel, then report back to main agent.
+- If you're given a Github URL, use [`repomix`](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple `Explorer` subagents to explore it in parallel, then report back to main agent.

package/templates/claude/commands/skill/optimize/auto.md

@@ -0,0 +1,25 @@
+---
+description: Optimize an existing agent skill [auto]
+argument-hint: [skill-name] [prompt]
+---
+
+Think harder.
+Use `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+
+## Arguments
+SKILL: $1 (default: `*`)
+PROMPT: $2 (default: empty)
+
+## Your mission
+Optimize an existing skill in `.claude/skills/${SKILL}` directory. 
+Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
+`SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
+
+**IMPORTANT:**
+- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches Claude how to perform a specific development task, not what a tool does.
+- Claude Code can activate multiple skills automatically to achieve the user's request.
+
+## Additional instructions
+<additional-instructions>$PROMPT</additional-instructions>