claudeguide-engineer 1.14.8

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

@@ -0,0 +1,15 @@
+---
+description: ⚡⚡⚡⚡ Analyze the codebase and create initial documentation
+---
+
+## Mission
+Use `docs-manager` agent to analyze the codebase and 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.
+
+**IMPORTANT**: **Do not** start implementing.

package/.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/.claude/commands/docs/update.md

@@ -0,0 +1,23 @@
+---
+description: ⚡⚡⚡ Analyze the codebase and update documentation
+---
+
+Use `docs-manager` agent to analyze the codebase and 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>
+
+## Important
+- Use `docs/` directory as the source of truth for documentation.
+
+**IMPORTANT**: **Do not** start implementing.

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

@@ -0,0 +1,20 @@
+---
+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, analyze and find the root causes of the issues, then report back to main agent.
+2. Use `scout` subagent to analyze the codebase and find the exact location of the issues, then 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. Start implementing the fix based the reports and solutions.
+5. 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.
+
+## Notes
+- If `gh` command is not available, instruct the user to install and authorize GitHub CLI first.

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

@@ -0,0 +1,19 @@
+---
+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. If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
+2. Use `debugger` subagent to find the root cause of the issues and report back to main agent.
+3. Use `problem-solving` skills to tackle the issues.
+4. Start implementing the fix based the reports and solutions.
+5. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
+6. If there are issues or failed tests, repeat from step 2.
+7. 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/.claude/commands/fix/hard.md

@@ -0,0 +1,43 @@
+---
+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:
+
+If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
+
+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 general agent (main agent) to implement the plan step by step.
+5. Use `tester` subagent to write test cases and run the tests, make sure it works, then report back to main agent.
+6. 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.
+7. Repeat the process until all tests pass or no more issues are reported.
+8. After finishing, delegate to `code-reviewer` subagent to review code. 
+   If there are critical issues, ask main agent to improve the code and test everything again.
+   Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+9. 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.
+1.  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**:
+- You can always generate images with `ai-multimodal` skills on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skills to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use `ImageMagick` skill or similar tools as needed.

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

@@ -0,0 +1,20 @@
+---
+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. Use `debugger` subagent to read `./logs.txt` file, analyze and find the root causes of the issues, then report back to main agent.
+   If `./logs.txt` file is not available, reproduce the issue and pipe the logs to `./logs.txt` file.
+2. Use `scout` subagent to analyze the codebase and find the exact location of the issues, then 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. Start implementing the fix based the reports and solutions.
+5. 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.

package/.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.

package/.claude/commands/fix/types.md

@@ -0,0 +1,9 @@
+---
+description: ⚡ Fix type errors
+---
+
+Run `bun run typecheck` or `tsc` or `npx tsc` and fix all type errors.
+
+## Rules
+- Fix all of type errors and repeat the process until there are no more type errors.
+- Do not use `any` just to pass the type check.

package/.claude/commands/fix/ui.md

@@ -0,0 +1,35 @@
+---
+description: ⚡⚡ Analyze and fix UI issues
+argument-hint: [issue]
+---
+
+Use `ui-ux-designer` subagent to read and analyze `./docs/design-guidelines.md` then fix the following issues:
+<issue>$ARGUMENTS</issue>
+
+## Workflow
+If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
+
+1. Use `ui-ux-designer` subagent to implement the fix step by step.
+2. Use screenshot capture tools along with `ai-multimodal` skill to take screenshots of the implemented fix (at the exact parent container, don't take screenshot of the whole page) and use the appropriate Gemini analysis skills (`ai-multimodal`, `video-analysis`, or `document-extraction`) to analyze those outputs so the result matches the design guideline and addresses all issues.
+  - If the issues are not addressed, repeat the process until all issues are addressed.
+3. Use `chrome-devtools` skill to analyze the implemented fix and make sure it matches the design guideline.
+4. Use `tester` agent to test the fix and compile the code to make sure it works, then report back to main agent.
+  - If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.
+5. 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.
+6. 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**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use `ImageMagick` skill or similar tools as needed.
+- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

package/.claude/commands/fix.md

@@ -0,0 +1,12 @@
+---
+description: ⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY]
+argument-hint: [issues]
+---
+
+If there is a markdown implementation plan already, use `/code <path-to-plan>` slash command to implement it.
+
+Else: 
+- Analyze the issues and ask for more details if needed.
+- Decide to use `/fix:fast` or `/fix:hard` SlashCommands based on the complexity.
+- Execute SlashCommand: `/fix:fast <detailed-instructions-prompt>` or `/fix:hard <detailed-instructions-prompt>`
+- Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the issue in detail based on the provided issue description.

package/.claude/commands/git/cm.md

@@ -0,0 +1,5 @@
+---
+description: Stage all files and create a commit.
+---
+Use `git-manager` agent to stage all files and create a commit.
+**IMPORTANT: DO NOT push the changes to remote repository**

package/.claude/commands/git/cp.md

@@ -0,0 +1,4 @@
+---
+description: Stage, commit and push all code in the current branch
+---
+Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

package/.claude/commands/git/pr.md

@@ -0,0 +1,15 @@
+---
+description: Create a pull request
+argument-hint: [branch] [from-branch]
+---
+
+## Variables
+
+TO_BRANCH: $1 (defaults to `main`)
+FROM_BRANCH: $2 (defaults to current branch)
+
+## Workflow
+- Use `git-manager` agent to create a pull request from {FROM_BRANCH} to {TO_BRANCH} branch.
+
+## Notes
+- If `gh` command is not available, instruct the user to install and authorize GitHub CLI first.

package/.claude/commands/integrate/polar.md

@@ -0,0 +1,28 @@
+---
+description: ⚡⚡ Implement payment integration with Polar.sh
+argument-hint: [tasks]
+---
+
+Think harder.
+Activate `payment-integration` skill.
+Plan & start implementing payment integration with [Polar.sh](https://polar.sh/docs/llms-full.txt) 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 <plan>` to implement the plan.

package/.claude/commands/integrate/sepay.md

@@ -0,0 +1,28 @@
+---
+description: ⚡⚡ Implement payment integration with SePay.vn
+argument-hint: [tasks]
+---
+
+Think harder.
+Activate `payment-integration` skill.
+Plan & start implementing payment integration with [https://developer.sepay.vn/vi](https://developer.sepay.vn/vi) 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 <plan>` to implement the plan.

package/.claude/commands/journal.md

@@ -0,0 +1,5 @@
+---
+description: ⚡ Write some journal entries.
+---
+
+Use the `journal-writer` subagent to explore the memories and recent code changes, and write some journal entries.

package/.claude/commands/plan/ci.md

@@ -0,0 +1,18 @@
+---
+description: Analyze Github Actions logs and provide a plan to fix the issues
+argument-hint: [github-actions-url]
+---
+
+Activate `planning` skill.
+
+## Github Actions URL
+ $ARGUMENTS
+
+Use the `planner` subagent to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
+
+**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.
+
+**IMPORTANT:** Ask the user for confirmation before implementing.
+**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/.claude/commands/plan/cro.md

@@ -0,0 +1,56 @@
+---
+description: Create a CRO plan for the given content
+argument-hint: [issues]
+---
+
+You are an expert in conversion optimization. Analyze the content based on the given issues:
+<issues>$ARGUMENTS</issues>
+
+Activate `planning` skill.
+
+**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.
+
+## 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 screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description.
+- If the user provides a URL, use `web_fetch` tool to fetch the content of the URL and analyze the current issues.
+- You can use screenshot capture tools along with `ai-multimodal` skill to capture screenshots of the exact parent container and analyze the current issues with the appropriate Gemini analysis skills (`ai-multimodal`, `gemini-video-understanding`, or `gemini-document-processing`).
+- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+- Use `planner` agent to create a comprehensive CRO plan following the progressive disclosure structure:
+  - Create a directory `plans/YYYYMMDD-HHmm-plan-name` (example: `plans/20251101-1505-authentication-and-profile-implementation`).
+  - 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).
+  - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+- Do not start implementing the CRO plan yet, wait for the user to approve the plan first.
+
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+**IMPORTANT:** In reports, list any unresolved questions at the end, if any.

package/.claude/commands/plan/fast.md

@@ -0,0 +1,46 @@
+---
+description: ⚡⚡ No research. Only analyze and create an implementation plan
+argument-hint: [task]
+---
+
+Think.
+Activate `planning` skill.
+
+## Your mission
+<task>
+$ARGUMENTS
+</task>
+
+## Workflow
+Use `planner` subagent to:
+1. Create a directory named `plans/YYYYMMDD-HHmm-plan-name` (eg. `plans/20251101-1505-authentication-and-profile-implementation`).
+   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.
+
+## Output Requirements
+
+**Plan Directory Structure**
+```
+plans/
+└── YYYYMMDD-HHmm-plan-name/
+    ├── reports/
+    │   ├── XX-report.md
+    │   └── ...
+    ├── plan.md
+    ├── phase-XX-phase-name-here.md
+    └── ...
+```
+
+**Plan File Specification**
+- Save the overview access point at `plans/YYYYMMDD-HHmm-plan-name/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 `plans/YYYYMMDD-HHmm-plan-name/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 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/.claude/commands/plan/hard.md

@@ -0,0 +1,57 @@
+---
+description: ⚡⚡⚡ Research, analyze, and create an implementation plan
+argument-hint: [task]
+---
+
+Think harder.
+Activate `planning` skill.
+
+## Your mission
+<task>
+$ARGUMENTS
+</task>
+
+## Workflow
+1. Create a directory named `plans/YYYYMMDD-HHmm-plan-name` (eg. `plans/20251101-1505-authentication-and-profile-implementation`).
+   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
+
+## Output Requirements
+
+**Plan Directory Structure**
+```
+plans/
+└── YYYYMMDD-HHmm-plan-name/
+    ├── 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**
+- Save the overview access point at `plans/YYYYMMDD-HHmm-plan-name/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 `plans/YYYYMMDD-HHmm-plan-name/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/.claude/commands/plan/two.md

@@ -0,0 +1,30 @@
+---
+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 named `plans/YYYYMMDD-HHmm-plan-name` (eg. `plans/20251101-1505-authentication-and-profile-implementation`).
+   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
+
+## 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/.claude/commands/plan.md

@@ -0,0 +1,23 @@
+---
+description: ⚡⚡⚡ Intelligent plan creation with prompt enhancement
+argument-hint: [task]
+---
+
+## Your mission
+<task>
+$ARGUMENTS
+</task>
+
+## Workflow
+- Analyze the given task and 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/.claude/commands/review/codebase.md

@@ -0,0 +1,49 @@
+---
+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 `plans/YYYYMMDD-HHmm-plan-name` (example: `plans/20251101-1505-authentication-and-profile-implementation`).
+  - 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**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.