@macpaw/cctk 1.0.0-beta.1

package/templates/claude/commands/coding-level.md

@@ -0,0 +1,37 @@
+Enable or disable coding level guidelines for expert-level output.
+
+## Usage
+
+Set `codingLevel` in `.claude/.cctk.json`:
+
+```json
+{
+  "codingLevel": true,
+  ...
+}
+```
+
+To disable:
+```json
+{
+  "codingLevel": false,
+  ...
+}
+```
+
+## How It Works
+
+1. Set `codingLevel: true` in `.claude/.cctk.json`
+2. Guidelines are **automatically injected** on every session start
+3. No manual activation needed - it just works!
+
+## What It Does
+
+When enabled, Claude will:
+- Communicate at expert level - maximum efficiency
+- Use precise technical terminology without over-explanation
+- Skip basic concepts - assume deep understanding
+- Focus on trade-offs, edge cases, and non-obvious implications
+- Provide direct answers without unnecessary context
+- Challenge assumptions and point out potential issues
+- Optimize for signal-to-noise ratio

package/templates/claude/commands/content/cro.md

@@ -0,0 +1,41 @@
+---
+description: Analyze the current content and optimize for conversion
+argument-hint: [issues]
+---
+
+You are an expert in conversion optimization. Analyze the content based on reported issues:
+<issues>$ARGUMENTS</issues>
+
+## Conversion Optimization Framework
+
+1. Headline 4-U Formula: Useful, Unique, Urgent, Ultra-specific (80% won't read past this)
+2. Above-Fold Value Proposition: Customer problem focus, no company story, zero scroll required
+3. CTA First-Person Psychology: "Get MY Guide" vs "Get YOUR Guide" (90% more clicks)
+4. 5-Field Form Maximum: Every field kills conversions, progressive profiling for the rest
+5. Message Match Precision: Ad copy, landing page headline, broken promises = bounce
+6. Social Proof Near CTAs: Testimonials with faces/names, results, placed at decision points
+7. Cognitive Bias Stack: Loss aversion (fear), social proof (FOMO), anchoring (pricing)
+8. PAS Copy Framework: Problem > Agitate > Solve, emotion before logic
+9. Genuine Urgency Only: Real deadlines, actual limits, fake timers destroy trust forever
+10. Price Anchoring Display: Show expensive option first, make real price feel like relief
+11. Trust Signal Clustering: Security badges, guarantees, policies all visible together
+12. Visual Hierarchy F-Pattern: Eyes scan F-shape, put conversions in the path
+13. Lead Magnet Hierarchy: Templates > Checklists > Guides (instant > delayed gratification)
+14. Objection Preemption: Address top 3 concerns before they think them, FAQ near CTA
+15. Mobile Thumb Zone: CTAs where thumbs naturally rest, not stretching required
+16. One-Variable Testing: Change one thing, measure impact, compound wins over time
+17. Post-Conversion Momentum: Thank you page sells next step while excitement peaks
+18. Cart Recovery Sequence: Email in 1 hour, retarget in 4 hours, incentive at 24 hours
+19. Reading Level Grade 6: Smart people prefer simple, 11-word sentences, short paragraphs
+20. TOFU/MOFU/BOFU Logic: Awareness content ≠ decision content, match intent precisely
+21. White Space = Focus: Empty space makes CTAs impossible to miss, crowded = confused
+22. Benefit-First Language: Features tell, benefits sell, transformations compel
+23. Micro-Commitment Ladder: Small yes leads to big yes, start with email only
+24. Performance Tracking Stack: Heatmaps show problems, recordings show why, events show what
+25. Weekly Optimization Ritual: Review metrics Monday, test Tuesday, iterate or scale
+
+## Workflow
+
+- If the user provides a URL, use `web_fetch` tool to fetch the content and analyze current issues.
+- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+- Use `copywriter` agent to write the enhanced copy into the code files, then report back to main agent.

package/templates/claude/commands/content/enhance.md

@@ -0,0 +1,12 @@
+---
+description: Analyze the current copy issues and enhance it
+argument-hint: [issues]
+---
+
+Enhance the copy based on reported issues:
+<issues>$ARGUMENTS</issues>
+
+## Workflow
+
+- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+- Use `copywriter` agent to write the enhanced copy into the code files, then report back to main agent.

package/templates/claude/commands/content/fast.md

@@ -0,0 +1,11 @@
+---
+description: Write creative & smart copy [FAST]
+argument-hint: [user-request]
+---
+
+Write creative & smart copy for this user request:
+<user_request>$ARGUMENTS</user_request>
+
+## Workflow
+
+- Use `copywriter` agent to write the copy, then report back to main agent.

package/templates/claude/commands/content/good.md

@@ -0,0 +1,14 @@
+---
+description: Write good creative & smart copy [GOOD]
+argument-hint: [user-request]
+---
+
+Write good creative & smart copy for this user request:
+<user_request>$ARGUMENTS</user_request>
+
+## Workflow
+
+- Use multiple `researcher` agents in parallel to search for relevant information, then report back to main agent.
+- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+- Use `planner` agent to plan the copy, make sure it can satisfy the user request.
+- Use `copywriter` agent to write the copy based on the plan, then report back to main agent.

package/templates/claude/commands/cook/auto/fast.md

@@ -0,0 +1,26 @@
+---
+description: ⚡ No research. Only scout, plan & implement ["trust me bro"]
+argument-hint: [tasks-or-prompt]
+---
+
+Think harder to plan & start working on these tasks 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.
+
+---
+
+**IMPORTANT**: Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+
+- **Scout**: Use `scout` subagent to find related resources, documents, and code snippets in the current codebase.
+- **Plan**: Trigger slash command `/plan:fast <detailed-instruction-prompt>` to create an implementation plan based on the reports from `scout` subagent.
+- **Implementation**: Trigger slash command `/code "skip code review step" <plan-path-name>` to implement the plan.

package/templates/claude/commands/cook/auto/parallel.md

@@ -0,0 +1,49 @@
+---
+description: ⚡⚡⚡ Plan parallel phases & execute with fullstack-developer agents
+argument-hint: [tasks]
+---
+
+**Ultrathink parallel** to implement: <tasks>$ARGUMENTS</tasks>
+
+**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
+
+## Workflow
+
+### 1. Research (Optional)
+- Use max 2 `researcher` agents in parallel if tasks complex
+- Use `/scout:ext` to search codebase
+- Keep reports ≤150 lines
+
+### 2. Parallel Planning
+- Trigger `/plan:parallel <detailed-instruction>`
+- Wait for plan with dependency graph, execution strategy, file ownership matrix
+
+### 3. Parallel Implementation
+- Read `plan.md` for dependency graph
+- Launch multiple `fullstack-developer` agents in PARALLEL for concurrent phases
+  - Example: "Phases 1-3 parallel" → launch 3 agents simultaneously
+  - Pass phase file path: `{plan-dir}/phase-XX-*.md`
+  - Include environment info
+- Wait for all parallel phases complete before dependent phases
+- Sequential phases: launch one agent at a time
+
+### 4. Testing
+- Use `tester` subagent for full test suite
+- NO fake data/mocks/cheats
+- If fail: use `debugger`, fix, repeat
+
+### 5. Code Review
+- Use `code-reviewer` for all changes
+- If critical issues: fix, retest
+
+### 6. Project Management & Docs
+- If approved: use `project-manager` + `docs-manager` in parallel
+- Update plan files, docs, roadmap
+- If rejected: fix and repeat
+
+### 7. Final Report
+- Summary of all parallel phases
+- Guide to get started
+- Ask to commit (use `git-manager` if yes)
+
+**Example:** Phases 1-3 parallel → Launch 3 fullstack-developer agents → Wait → Phase 4 sequential

package/templates/claude/commands/cook/auto.md

@@ -0,0 +1,15 @@
+---
+description: ⚡⚡ Implement a feature automatically ("trust me bro")
+argument-hint: [tasks]
+---
+
+**Ultrathink** to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+**IMPORTANT:** Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. Trigger slash command `/plan <detailed-instruction-prompt>` to create an implementation plan based on the given tasks.
+2. Trigger slash command `/code <plan>` to implement the plan.
+3. Finally use `AskUserQuestion` tool to ask user if he wants to commit to git repository, if yes trigger `/git:cm` slash command to create a commit.

package/templates/claude/commands/cook.md

@@ -0,0 +1,101 @@
+---
+description: ⚡⚡⚡ Implement a feature [step by step]
+argument-hint: [tasks]
+---
+
+Think harder to plan & start working on these tasks 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. 
+- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- 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.
+
+---
+
+## Your Approach
+
+1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+### Fullfill the request
+
+* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If you don't have any questions, start the next step.
+
+**IMPORTANT:** Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, 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
+
+### Plan
+
+*. Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an implementation plan using 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).
+
+### Implementation
+
+* Use `/code` Slash Command to implement the plan step by step, follow the implementation plan in `./plans` directory.
+* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `media-processing` skill for image editing (crop, resize, remove background) if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, **make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. 
+* 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.
+
+### Project Management & Documentation
+
+**If user approves the changes:**
+* Use `project-manager` and `docs-manager` subagents in parallel to update the project progress and documentation:
+  * Use `project-manager` subagent to update the project progress and task status in the given plan file.
+  * Use `docs-manager` subagent to update the docs in `./docs` directory if needed.
+  * Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+**If user rejects the changes:**
+* Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
+
+### Onboarding
+
+* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
+* Help the user to configure (if needed) step by step, ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### 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.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**REMEMBER**:
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.

package/templates/claude/commands/debug.md

@@ -0,0 +1,13 @@
+---
+description: ⚡⚡ Debugging technical issues and providing solutions.
+argument-hint: [issues]
+---
+ 
+**Reported Issues**:
+ $ARGUMENTS
+
+Use the `debugger` subagent to find the root cause of the issues, then analyze and explain the reports to the user.
+
+**IMPORTANT**: **Do not** implement the fix automatically.
+**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 outputs.

package/templates/claude/commands/docs/init.md

@@ -0,0 +1,37 @@
+---
+description: ⚡⚡⚡⚡ Analyze the codebase and create initial documentation
+---
+
+## Phase 1: Parallel Codebase Scouting
+
+1. Scan the codebase and calculate the number of files with LOC in each directory (skip credentials, cache or external modules directories, such as `.claude`, `.opencode`, `.git`, `tests`, `node_modules`, `__pycache__`, `secrets`, etc.)
+2. Target directories **that actually exist** - adapt to project structure, don't hardcode paths
+3. Main agent spawns multiple `scout` subagents via Task tool:
+   - Write a detailed instructions prompt for each scout subagent with exact directories or files it should read
+   - Each scout subagent has less than 200K tokens of context window
+   - Amount of scouts depends on the current system resources available and project size in step 1
+   - Each scout subagent must return a detailed summary report to a main agent
+5. Main agent merges scout reports into context summary and delegate to `docs-manager` agent to update documentation (next phase)
+
+## Phase 2: Documentation Creation (docs-manager Agent)
+
+Pass the gathered file list to `docs-manager` agent to create initial documentation:
+- `docs/project-overview-pdr.md`: Project overview and PDR (Product Development Requirements)
+- `docs/codebase-summary.md`: Codebase summary
+- `docs/code-standards.md`: Codebase structure and code standards
+- `docs/system-architecture.md`: System architecture
+- Update `README.md` with initial documentation (keep it under 300 lines)
+
+Use `docs/` directory as the source of truth for documentation.
+
+## Phase 3: Size Check (Post-Generation)
+
+After docs-manager completes:
+1. Run `wc -l docs/*.md 2>/dev/null | sort -rn` to check LOC
+2. Use `docs.maxLoc` from session context (default: 800)
+3. For files exceeding limit:
+   - Report which files exceed and by how much
+   - docs-manager should have already split proactively per Section 6 guidelines
+   - If still oversized, ask user: split now or accept as-is?
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/claude/commands/docs/summarize.md

@@ -0,0 +1,22 @@
+---
+description: ⚡ Analyze the codebase and update documentation
+argument-hint: [focused-topics] [should-scan-codebase]
+---
+
+Use `docs-manager` agent to analyze the codebase based on `docs/codebase-summary.md` and respond with a summary report.
+
+## Arguments:
+$1: Focused topics (default: all)
+$2: Should scan codebase (`Boolean`, default: `false`)
+
+## Focused Topics:
+<focused_topics>$1</focused_topics>
+
+## Should Scan Codebase:
+<should_scan_codebase>$2</should_scan_codebase>
+
+## Important:
+- Use `docs/` directory as the source of truth for documentation.
+- Do not scan the entire codebase unless the user explicitly requests it.
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/claude/commands/docs/update.md

@@ -0,0 +1,78 @@
+---
+description: ⚡⚡⚡ Analyze the codebase and update documentation
+---
+
+## Phase 1: Parallel Codebase Scouting
+
+1. Scan the codebase and calculate the number of files with LOC in each directory (skip credentials, cache or external modules directories, such as `.claude`, `.opencode`, `.git`, `tests`, `node_modules`, `__pycache__`, `secrets`, etc.)
+2. Target directories **that actually exist** - adapt to project structure, don't hardcode paths
+3. Main agent spawns multiple `scout` subagents via Task tool:
+   - Write a detailed instructions prompt for each scout subagent with exact directories or files it should read
+   - Each scout subagent has less than 200K tokens of context window
+   - Amount of scouts depends on the current system resources available and project size in step 1
+   - Each scout subagent must return a detailed summary report to a main agent
+5. Main agent merges scout reports into context summary and delegate to `docs-manager` agent to update documentation (next phase)
+
+## Phase 1.5: Parallel Documentation Reading
+
+**You (main agent) must spawn readers** - subagents cannot spawn subagents.
+
+1. Count docs: `ls docs/*.md 2>/dev/null | wc -l`
+2. Get LOC: `wc -l docs/*.md 2>/dev/null | sort -rn`
+3. Strategy:
+   - 1-3 files: Skip parallel reading, docs-manager reads directly
+   - 4-6 files: Spawn 2-3 `Explore` agents
+   - 7+ files: Spawn 4-5 `Explore` agents (max 5)
+4. Distribute files by LOC (larger files get dedicated agent)
+5. Each agent prompt: "Read these docs, extract: purpose, key sections, areas needing update. Files: {list}"
+6. Merge results into context for docs-manager
+
+### Workload Distribution Example
+
+| Agent | Files | Est. LOC |
+|-------|-------|----------|
+| 1 | codebase-summary.md (800) | 800 |
+| 2 | system-architecture.md (400), code-standards.md (300) | 700 |
+| 3 | project-overview-pdr.md (500), project-roadmap.md (200) | 700 |
+
+## Phase 2: Documentation Update (docs-manager Agent)
+
+Pass the gathered file list to `docs-manager` agent to update documentation:
+- `README.md`: Update README (keep it under 300 lines)
+- `docs/project-overview-pdr.md`: Update project overview and PDR (Product Development Requirements)
+- `docs/codebase-summary.md`: Update codebase summary
+- `docs/code-standards.md`: Update codebase structure and code standards
+- `docs/system-architecture.md`: Update system architecture
+- `docs/project-roadmap.md`: Update project roadmap
+- `docs/deployment-guide.md` [optional]: Update deployment guide
+- `docs/design-guidelines.md` [optional]: Update design guidelines
+
+## Additional requests
+<additional_requests>
+  $ARGUMENTS
+</additional_requests>
+
+## Phase 3: Size Check (Post-Update)
+
+After docs-manager completes:
+1. Run `wc -l docs/*.md 2>/dev/null | sort -rn` to check LOC
+2. Use `docs.maxLoc` from session context (default: 800)
+3. For files exceeding limit:
+   - Report which files exceed and by how much
+   - docs-manager should have already split proactively per Section 6 guidelines
+   - If still oversized, ask user: split now or accept as-is?
+
+## Phase 4: Documentation Validation (Post-Update)
+
+Run validation to detect potential hallucinations:
+1. Run: `node .claude/scripts/validate-docs.cjs docs/`
+2. Display validation report (warnings only, non-blocking)
+3. Checks performed:
+   - Code references: Verify `functionName()` and `ClassName` exist in codebase
+   - Internal links: Verify `[text](./path.md)` links point to existing files
+   - Config keys: Verify `ENV_VAR` mentioned in docs exist in `.env.example`
+
+## Important
+- Use `docs/` directory as the source of truth for documentation.
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/claude/commands/fix/ci.md

@@ -0,0 +1,17 @@
+---
+description: ⚡ Analyze Github Actions logs and fix issues
+argument-hint: [github-actions-url]
+---
+
+## Github Actions URL
+<url>$ARGUMENTS</url>
+
+## Workflow
+1. Use `debugger` subagent to read the github actions logs with `gh` command, analyze and find the root cause of the issues and report back to main agent.
+2. Start implementing the fix based the reports and solutions.
+3. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
+4. If there are issues or failed tests, repeat from step 2.
+5. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+
+## Notes
+- If `gh` command is not available, instruct the user to install and authorize GitHub CLI first.

package/templates/claude/commands/fix/fast.md

@@ -0,0 +1,18 @@
+---
+description: ⚡ Analyze and fix small issues [FAST]
+argument-hint: [issues]
+---
+
+Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+## Mission
+**Think hard** to analyze and fix these issues:
+<issues>$ARGUMENTS</issues>
+
+## Workflow
+1. Use `debugger` subagent to find the root cause of the issues and report back to main agent.
+2. Activate `debugging` skills and `problem-solving` skills to tackle the issues.
+3. Start implementing the fix based the reports and solutions.
+4. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
+5. If there are issues or failed tests, repeat from step 1.
+6. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

package/templates/claude/commands/fix/hard.md

@@ -0,0 +1,35 @@
+---
+description: ⚡⚡⚡ Use subagents to plan and fix hard issues
+argument-hint: [issues]
+---
+
+**Ultrathink** to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
+<issues>$ARGUMENTS</issues>
+
+## Workflow:
+
+### Fullfill the request
+**Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If you don't have any questions, start the next step.
+
+### Fix the issue
+
+Use `sequential-thinking` skill to break complex problems into sequential thought steps.
+Use `problem-solving` skills to tackle the issues.
+Analyze the skills catalog and activate other skills that are needed for the task during the process.
+
+1. Use `debugger` subagent to find the root cause of the issues and report back to main agent.
+2. Use `researcher` subagent to research quickly about the root causes on the internet (if needed) and report back to main agent.
+3. Use `planner` subagent to create an implementation plan based on the reports, then report back to main agent.
+4. Then use `/code` SlashCommand to implement the plan step by step.
+5. 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.
+  - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+  - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**REMEMBER**:
+- For image editing (removing background, adjusting, cropping), use `ImageMagick` skill or similar tools as needed.

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

@@ -0,0 +1,26 @@
+---
+description: ⚡ Analyze logs and fix issues
+argument-hint: [issue]
+---
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+## Mission
+<issue>$ARGUMENTS</issue>
+
+## Workflow
+1. Check if `./logs.txt` exists:
+   - If missing, set up permanent log piping in project's script config (`package.json`, `Makefile`, `pyproject.toml`, etc.):
+     - **Bash/Unix**: append `2>&1 | tee logs.txt`
+     - **PowerShell**: append `*>&1 | Tee-Object logs.txt`
+   - Run the command to generate logs
+2. Use `debugger` subagent to analyze `./logs.txt` and find root causes:
+   - Use `Grep` with `head_limit: 30` to read only last 30 lines (avoid loading entire file)
+   - If insufficient context, increase `head_limit` as needed
+3. Use `scout` subagent to analyze the codebase and find the exact location of the issues, then report back to main agent.
+4. Use `planner` subagent to create an implementation plan based on the reports, then report back to main agent.
+5. Start implementing the fix based the reports and solutions.
+6. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
+7. Use `code-reviewer` subagent to quickly review the code changes and make sure it meets requirements, then report back to main agent.
+8. If there are issues or failed tests, repeat from step 3.
+9. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

package/templates/claude/commands/fix/parallel.md

@@ -0,0 +1,54 @@
+---
+description: ⚡⚡ Analyze & fix issues with parallel fullstack-developer agents
+argument-hint: [issues]
+---
+
+**Ultrathink parallel** to fix: <issues>$ARGUMENTS</issues>
+
+**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
+
+## Workflow
+
+### 1. Issue Analysis
+- Use `debugger` subagent to analyze root causes
+- Use `/scout:ext` to find related files
+- Categorize issues by scope/area (frontend, backend, auth, payments, etc.)
+- Identify dependencies between issues
+
+### 2. Parallel Fix Planning
+- Trigger `/plan:parallel <detailed-fix-instructions>` for parallel-executable fix plan
+- Wait for plan with dependency graph, execution strategy, file ownership matrix
+- Group independent fixes for parallel execution
+- Sequential fixes for dependent issues
+
+### 3. Parallel Fix Implementation
+- Read `plan.md` for dependency graph
+- Launch multiple `fullstack-developer` agents in PARALLEL for independent fixes
+  - Example: "Fix auth + Fix payments + Fix UI" → launch 3 agents simultaneously
+  - Pass phase file path: `{plan-dir}/phase-XX-*.md`
+  - Include environment info
+- Wait for all parallel fixes complete before dependent fixes
+- Sequential fixes: launch one agent at a time
+
+### 4. Testing
+- Use `tester` subagent for full test suite
+- NO fake data/mocks/cheats
+- Verify all issues resolved
+- If fail: use `debugger`, fix, repeat
+
+### 5. Code Review
+- Use `code-reviewer` for all changes
+- Verify fixes don't introduce regressions
+- If critical issues: fix, retest
+
+### 6. Project Management & Docs
+- If approved: use `project-manager` + `docs-manager` in parallel
+- Update plan files, docs, roadmap
+- If rejected: fix and repeat
+
+### 7. Final Report
+- Summary of all fixes from parallel phases
+- Verification status per issue
+- Ask to commit (use `git-manager` if yes)
+
+**Example:** Fix 1 (auth) + Fix 2 (payments) + Fix 3 (UI) → Launch 3 fullstack-developer agents → Wait → Fix 4 (integration) sequential

package/templates/claude/commands/fix/test.md

@@ -0,0 +1,20 @@
+---
+description: ⚡⚡ Run test suite and fix issues
+argument-hint: [issues]
+---
+
+Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+## Reported Issues:
+<issues>$ARGUMENTS</issues>
+
+## Workflow:
+1. Use `tester` subagent to compile the code and fix all syntax errors if any.
+2. Use `tester` subagent to run the tests and report back to main agent.
+3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then report back to main agent.
+4. Use `planner` subagent to create an implementation plan based on the reports, then report back to main agent.
+5. Use main agent to implement the plan step by step.
+6. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
+6. Use `code-reviewer` subagent to quickly review the code changes and make sure it meets requirements, then report back to main agent.
+7. If there are issues or failed tests, repeat from step 2.
+8. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.