thanh-kit 2.5.4 → 2.5.5

package/templates/commands/plan/fast.md

@@ -1,82 +0,0 @@
----
-description: ⚡⚡ No research. Only analyze and create an implementation plan
-argument-hint: [task]
----
-
-Think.
-Activate `planning` skill.
-
-## Your mission
-<task>
-$ARGUMENTS
-</task>
-
-## Pre-Creation Check (Active vs Suggested Plan)
-
-Check the `## Plan Context` section in the injected context:
-- If "Plan:" shows a path → Active plan exists. Ask user: "Continue with this? [Y/n]"
-- If "Suggested:" shows a path → Branch-matched hint only. Ask if they want to activate or create new.
-- If "Plan: none" → Create new plan using naming from `## Naming` section.
-
-## Workflow
-Use `planner` subagent to:
-1. If creating new: Create directory using `Plan dir:` from `## Naming` section, then run `node .claude/scripts/set-active-plan.cjs {plan-dir}`
-   If reusing: Use the active plan path from Plan Context.
-   Make sure you pass the directory path to every subagent during the process.
-2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
-3. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
-4. Gathers all information and create an implementation plan of this task.
-5. Ask user to review the plan.
-
-## Context Reminder (MANDATORY)
-
-**IMPORTANT:** After plan creation, you MUST remind the user with the **full absolute path**:
-
-> **Best Practice:** Run `/clear` before implementing to start with fresh context.
-> Then run:
-> ```
-> /cook --auto {ABSOLUTE_PATH_TO_PLAN_DIR}/plan.md
-> ```
-> *(Replace with actual absolute path, e.g., `/home/user/project/plans/260203-1234-feature/plan.md`)*
-
-**Why `--auto`?** Fast planning pairs with fast execution - skips review gates.
-**Why absolute path?** After `/clear`, the new session loses context. Worktree paths won't be discoverable without the full path.
-
-This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan with the actual absolute path.
-
-## Output Requirements
-
-**Plan Directory Structure** (use `Plan dir:` from `## Naming` section)
-```
-{plan-dir}/
-├── reports/
-│   ├── XX-report.md
-│   └── ...
-├── plan.md
-├── phase-XX-phase-name-here.md
-└── ...
-```
-
-**Plan File Specification**
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P2
-  effort: {sum of phases, e.g., 4h}
-  branch: {current git branch}
-  tags: [relevant, tags]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-- Save the overview access point at `{plan-dir}/plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
-- For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
-
-## Important Notes
-- **IMPORTANT:** Ensure token consumption efficiency while maintaining high quality.
-- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-- **IMPORTANT**: **Do not** start implementing.

package/templates/commands/plan/hard.md

@@ -1,108 +0,0 @@
----
-description: ⚡⚡⚡ Research, analyze, and create an implementation plan
-argument-hint: [task]
----
-
-Think harder.
-Activate `planning` skill.
-
-## Your mission
-<task>
-$ARGUMENTS
-</task>
-
-## Pre-Creation Check (Active vs Suggested Plan)
-
-Check the `## Plan Context` section in the injected context:
-- If "Plan:" shows a path → Active plan exists. Ask user: "Continue with this? [Y/n]"
-- If "Suggested:" shows a path → Branch-matched hint only. Ask if they want to activate or create new.
-- If "Plan: none" → Create new plan using naming from `## Naming` section.
-
-## Workflow
-1. If creating new: Create directory using `Plan dir:` from `## Naming` section, then run `node .claude/scripts/set-active-plan.cjs {plan-dir}`
-   If reusing: Use the active plan path from Plan Context.
-   Make sure you pass the directory path to every subagent during the process.
-2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
-3. Use multiple `researcher` agents (max 2 agents) in parallel to research for this task:
-   Each agent research for a different aspect of the task and are allowed to perform max 5 tool calls.
-4. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
-   **ONLY PERFORM THIS FOLLOWING STEP IF `codebase-summary.md` is not available or older than 3 days**: Use `/scout <instructions>` slash command to search the codebase for files needed to complete the task.
-5. Main agent gathers all research and scout report filepaths, and pass them to `planner` subagent with the prompt to create an implementation plan of this task.
-6. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
-
-## Post-Plan Validation (Optional)
-
-After plan creation, offer validation interview to confirm decisions before implementation.
-
-**Check `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`:**
-
-| Mode | Behavior |
-|------|----------|
-| `prompt` | Ask user: "Validate this plan with a brief interview?" → Yes (Recommended) / No |
-| `auto` | Automatically execute `/plan:validate {plan-path}` |
-| `off` | Skip validation step entirely |
-
-**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
-**If user chooses validation or mode is `auto`:** Execute `/plan:validate {plan-path}` SlashCommand.
-
-## Context Reminder (MANDATORY)
-
-**IMPORTANT:** If user skips validation (chooses "No" or mode is `off`), you MUST remind them with the **full absolute path**:
-
-> **Best Practice:** Run `/clear` before implementing to start with fresh context.
-> Then run:
-> ```
-> /cook {ABSOLUTE_PATH_TO_PLAN_DIR}/plan.md
-> ```
-> *(Replace with actual absolute path, e.g., `/home/user/project/plans/260203-1234-feature/plan.md`)*
-
-**Why no flag?** Thorough planning without validation needs interactive review gates.
-**Why absolute path?** After `/clear`, the new session loses context. Worktree paths won't be discoverable without the full path.
-
-This reminder is **NON-NEGOTIABLE** when validation is skipped - always output with the actual absolute path.
-
-## Output Requirements
-
-**Plan Directory Structure** (use `Plan dir:` from `## Naming` section)
-```
-{plan-dir}/
-├── research/
-│   ├── researcher-XX-report.md
-│   └── ...
-├── reports/
-│   ├── XX-report.md
-│   └── ...
-├── scout/
-│   ├── scout-XX-report.md
-│   └── ...
-├── plan.md
-├── phase-XX-phase-name-here.md
-└── ...
-```
-
-**Research Output Requirements**
-- Ensure every research markdown report remains concise (≤150 lines) while covering all requested topics and citations.
-
-**Plan File Specification**
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P2
-  effort: {sum of phases, e.g., 4h}
-  branch: {current git branch}
-  tags: [relevant, tags]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-- Save the overview access point at `{plan-dir}/plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
-- For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
-
-## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.

package/templates/commands/plan/parallel.md

@@ -1,145 +0,0 @@
----
-description: ⚡⚡⚡ Create detailed plan with parallel-executable phases
-argument-hint: [task]
----
-
-Think strategically about parallelization.
-Activate `planning` skill.
-
-## Your mission
-<task>
-$ARGUMENTS
-</task>
-
-## Workflow
-1. Create a directory using naming pattern from `## Naming` section in injected context.
-   Make sure you pass the directory path to every subagent during the process.
-2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
-3. Use multiple `researcher` agents (max 2 agents) in parallel to research for this task:
-   Each agent research for a different aspect of the task and are allowed to perform max 5 tool calls.
-4. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
-   **ONLY PERFORM THIS FOLLOWING STEP IF `codebase-summary.md` is not available or older than 3 days**: Use `/scout <instructions>` slash command to search the codebase for files needed to complete the task.
-5. Main agent gathers all research and scout report filepaths, and pass them to `planner` subagent with the prompt to create a parallel-optimized implementation plan.
-6. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
-
-## Post-Plan Validation (Optional)
-
-After plan creation, offer validation interview to confirm decisions before implementation.
-
-**Check `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`:**
-
-| Mode | Behavior |
-|------|----------|
-| `prompt` | Ask user: "Validate this plan with a brief interview?" → Yes (Recommended) / No |
-| `auto` | Automatically execute `/plan:validate {plan-path}` |
-| `off` | Skip validation step entirely |
-
-**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
-**If user chooses validation or mode is `auto`:** Execute `/plan:validate {plan-path}` SlashCommand.
-
-## Special Requirements for Parallel Execution
-
-**CRITICAL:** The planner subagent must create phases that:
-1. **Can be executed independently** - Each phase should be self-contained with no runtime dependencies on other phases
-2. **Have clear boundaries** - No file overlap between phases (each file should only be modified in ONE phase)
-3. **Separate concerns logically** - Group by architectural layer, feature domain, or technology stack
-4. **Minimize coupling** - Phases should communicate through well-defined interfaces only
-5. **Include dependency matrix** - Clearly document which phases must run sequentially vs in parallel
-
-**Parallelization Strategy:**
-- Group frontend/backend/database work into separate phases when possible
-- Separate infrastructure setup from application logic
-- Isolate different feature domains (e.g., auth vs profile vs payments)
-- Split by file type/directory (e.g., components vs services vs models)
-- Create independent test phases per module
-
-**Phase Organization Example:**
-```
-Phase 01: Database Schema (can run independently)
-Phase 02: Backend API Layer (can run independently)
-Phase 03: Frontend Components (can run independently)
-Phase 04: Integration Tests (depends on 01, 02, 03)
-```
-
-## Output Requirements
-
-**Plan Directory Structure** (use `Plan dir:` from `## Naming` section)
-```
-{plan-dir}/
-├── research/
-│   ├── researcher-XX-report.md
-│   └── ...
-├── reports/
-│   ├── XX-report.md
-│   └── ...
-├── scout/
-│   ├── scout-XX-report.md
-│   └── ...
-├── plan.md
-├── phase-XX-phase-name-here.md
-└── ...
-```
-
-**Research Output Requirements**
-- Ensure every research markdown report remains concise (≤150 lines) while covering all requested topics and citations.
-
-**Plan File Specification**
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P2
-  effort: {sum of phases, e.g., 4h}
-  branch: {current git branch}
-  tags: [relevant, tags]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-- Save the overview access point at `{plan-dir}/plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status, progress, parallelization group, and links to phase files.
-- For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order:
-  - Context links (reference parent plan, dependencies, docs)
-  - **Parallelization Info** (which phases can run concurrently, which must wait)
-  - Overview (date, description, priority, implementation status, review status)
-  - Key Insights
-  - Requirements
-  - Architecture
-  - **Related code files** (MUST be exclusive to this phase - no overlap with other phases)
-  - **File Ownership** (explicit list of files this phase owns/modifies)
-  - Implementation Steps
-  - Todo list
-  - Success Criteria
-  - **Conflict Prevention** (how this phase avoids conflicts with parallel phases)
-  - Risk Assessment
-  - Security Considerations
-  - Next steps
-
-**Main plan.md must include:**
-- Dependency graph showing which phases can run in parallel
-- Execution strategy (e.g., "Phases 1-3 parallel, then Phase 4")
-- File ownership matrix (which phase owns which files)
-
-## Context Reminder (MANDATORY)
-
-**IMPORTANT:** After plan creation, you MUST remind the user with the **full absolute path**:
-
-> **Best Practice:** Run `/clear` before implementing to start with fresh context.
-> Then run:
-> ```
-> /cook --parallel {ABSOLUTE_PATH_TO_PLAN_DIR}/plan.md
-> ```
-> *(Replace with actual absolute path, e.g., `/home/user/project/plans/260203-1234-feature/plan.md`)*
-
-**Why `--parallel`?** Parallel-optimized plan pairs with parallel execution - multiple agents work on independent phases.
-**Why absolute path?** After `/clear`, the new session loses context. Worktree paths won't be discoverable without the full path.
-
-This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan with the actual absolute path.
-
-## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT:** Do not start implementing.
-**IMPORTANT:** Each phase MUST have exclusive file ownership - no file can be modified by multiple phases.

package/templates/commands/plan/two.md

@@ -1,45 +0,0 @@
----
-description: ⚡⚡⚡⚡ Research & create an implementation plan with 2 approaches
-argument-hint: [task]
----
-
-Think harder.
-Activate `planning` skill.
-
-## Your mission
-Use the `planner` subagent to create 2 detailed implementation plans for this following task:
-<task>
- $ARGUMENTS
-</task>
-
-## Workflow
-1. First: Create a directory using naming pattern from `## Naming` section in injected context.
-   Make sure you pass the directory path to every subagent during the process.
-2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
-3. Use multiple `researcher` agents in parallel to research for this task, each agent research for a different aspect of the task and perform max 5 researches (max 5 tool calls).
-4. Use `scout` agent to search the codebase for files needed to complete the task.
-5. Main agent gathers all research and scout report filepaths, and pass them to `planner` subagent with the detailed instructions prompt to create an implementation plan of this task.
-  **Output:** Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-1. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
-
-## Plan File Specification
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P2
-  effort: {sum of phases, e.g., 4h}
-  branch: {current git branch}
-  tags: [relevant, tags]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-
-## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.

package/templates/commands/plan.md

@@ -1,30 +0,0 @@
----
-description: ⚡⚡⚡ Intelligent plan creation with prompt enhancement
-argument-hint: [task]
----
-
-## Your mission
-<task>
-$ARGUMENTS
-</task>
-
-## Pre-Creation Check (Active vs Suggested Plan Detection)
-
-Check the `## Plan Context` section in the injected context:
-- If "Plan:" shows a path → Active plan exists. Ask user: "Active plan found: {path}. Continue with this? [Y/n]"
-- If "Suggested:" shows a path → Branch-matched plan hint only. Ask user if they want to activate it or create new.
-- If "Plan: none" → Proceed to create new plan using naming pattern from `## Naming` section.
-
-## Workflow
-- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
-- Decide to use `/plan:fast` or `/plan:hard` SlashCommands based on the complexity.
-- Execute SlashCommand: `/plan:fast <detailed-instructions-prompt>` or `/plan:hard <detailed-instructions-prompt>`
-- Activate `planning` skill.
-- Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the task in detail based on the provided task description.
-
-## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.

package/templates/commands/scout/ext.md

@@ -1,39 +0,0 @@
----
-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
-
-## Configuration
-
-Read Gemini model from `.claude/.ck.json`: `gemini.model` (default: `gemini-3-flash-preview`)
-
-## 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 -y -m <gemini.model> "[prompt]"` (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/commands/scout.md

@@ -1,28 +0,0 @@
----
-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/commands/skill/add.md

@@ -1,36 +0,0 @@
----
-description: Add new reference files or scripts to a skill
-argument-hint: [skill-name] [reference-or-script-prompt]
----
-
-Think harder.
-Use `skill-creator` skill and `claude-code-guide` subagent.
-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/commands/skill/create.md

@@ -1,29 +0,0 @@
----
-description: Create a new agent skill
-argument-hint: [prompt-or-llms-or-github-url]
----
-
-Ultrathink.
-Use `skill-creator` skill and `claude-code-guide` subagent.
-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/commands/skill/fix-logs.md

@@ -1,22 +0,0 @@
----
-description: Fix the agent skill based on `logs.txt` file.
-argument-hint: [prompt-or-path-to-skill]
----
-
-Think harder.
-Use `skill-creator` skill and `claude-code-guide` subagent.
-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/commands/skill/optimize/auto.md

@@ -1,25 +0,0 @@
----
-description: Optimize an existing agent skill [auto]
-argument-hint: [skill-name] [prompt]
----
-
-Think harder.
-Use `skill-creator` skill and `claude-code-guide` subagent.
-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>

package/templates/commands/skill/optimize.md

@@ -1,34 +0,0 @@
----
-description: Optimize an existing agent skill
-argument-hint: [skill-name] [prompt]
----
-
-Think harder.
-Use `skill-creator` skill and `claude-code-guide` subagent.
-Use `docs-seeker` skills to search for documentation if needed.
-
-## Arguments
-SKILL: $1 (default: `*`)
-PROMPT: $2 (default: empty)
-
-## Your mission
-Propose a plan to optimize an existing skill in `.claude/skills/${SKILL}` directory. 
-When you finish, ask user to review your plan:
-- If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
-- If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
-
-## Additional instructions
-<additional-instructions>$PROMPT</additional-instructions>
-
-## Output Requirements
-An output implementation plan must also follow the progressive disclosure structure:
-- 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.
-- 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).
-
-**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.