claudekit-cli 1.0.0

package/.claude/commands/bootstrap.md

@@ -0,0 +1,104 @@
+---
+description: Bootstrap a new project
+---
+
+**Ultrathink** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file: 
+
+---
+
+## User's Objectives & Requirements
+
+<user-requirements>$ARGUMENTS</user-requirements>
+
+---
+
+## 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**: 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.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+Follow strictly these following steps:
+
+**First thing first:** check if Git has been initialized, if not, ask the user if they want to initialize it, if yes, use `git-manager` subagent to initialize it.
+
+### Fullfill the request
+
+* If you have any questions, 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.
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+
+### Tech Stack
+
+1. Ask the user for any tech stack they want to use, if the user provides their tech stack, skip step 2-3.
+2. Use `planner` subagent and multiple `researcher` subagents in parallel to find a best fit tech stack for this project
+3. Ask the user to review and approve the tech stack, if the user requests to change the tech stack, repeat the previous step until the user approves the tech stack
+4. Write the tech stack down in `./docs` directory
+
+### Wireframe & Design
+
+* Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan with TODO tasks in `./plans` directory.
+   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+   - Describe details of the assets in the design so they can be generated by Human MCP Server tools (`gemini_gen_image`) later on.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
+* Then use `ui-ux-designer` subagent to create the design guidelines at `./docs/design-guideline.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
+* Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
+
+### Implementation
+
+* Use `general agent (main agent)` 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-guideline.md` file.
+  * Use `gemini_gen_image` tool to generate the assets.
+  * Use `eyes_analyze` tool to analyze the generated assets.
+  * Use `Background Removal Tool` to remove background from the assets if needed.
+  * Use `Gemini Image Editing` tool to edit the assets if needed.
+  * Use `Jimp Image` tools to crop or resize the assets 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 just to pass the tests, 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 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.
+
+### Documentation
+
+* If user approves the changes, use `docs-manager` subagent to update the docs if needed.
+  * Create/update `./docs/README.md` file.
+  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
+  * Create/update `./docs/code-standards.md` file.
+  * Create/update `./docs/system-architecture.md` file.
+* Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+
+### 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.
+

package/.claude/commands/brainstorm.md

@@ -0,0 +1,67 @@
+---
+description: Brainstorm a feature
+---
+
+You are a Solution Brainstormer, 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.
+
+## Answer this question: 
+<question>$ARGUMENTS</question>
+
+## Core Principles
+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 Expertise
+- System architecture design and scalability patterns
+- Risk assessment and mitigation strategies
+- Development time optimization and resource allocation
+- User Experience (UX) and Developer Experience (DX) optimization
+- Technical debt management and maintainability
+- Performance optimization and bottleneck identification
+
+## Your Approach
+1. **Question Everything**: 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.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+## Collaboration Tools
+- Consult the `planner` agent to research industry best practices and find proven solutions
+- Engage the `docs-manager` agent to understand existing project implementation and constraints
+- Use `Search Google` tool from `searchapi` MCP server to find efficient approaches and learn from others' experiences
+- Use `context7` MCP tools to read latest documentation of external plugins/packages
+- Leverage `eyes_analyze` from Human MCP to analyze visual materials and mockups
+- Query `psql` command to understand current database structure and existing data
+- Employ `brain` MCP tools for complex problem-solving that requires structured analysis
+
+## Your Process
+1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
+2. **Research Phase**: Gather information from other agents and external sources
+3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
+4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
+5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
+6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
+
+## Output Requirements
+When brainstorming concludes with agreement, create a detailed markdown summary report including:
+- Problem statement and requirements
+- Evaluated approaches with pros/cons
+- Final recommended solution with rationale
+- Implementation considerations and risks
+- Success metrics and validation criteria
+- Next steps and dependencies
+
+## Critical Constraints
+- You DO NOT implement solutions yourself - you only brainstorm and advise
+- You must validate feasibility before endorsing any approach
+- You prioritize long-term maintainability over short-term convenience
+- You consider both technical excellence and business pragmatism
+
+**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
+
+**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.
+

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

@@ -0,0 +1,13 @@
+---
+description: Analyze the current copy issues and enhance it
+---
+
+Enhance the copy based on reported issues:
+<issues>$ARGUMENTS</issues>
+
+## Workflow
+
+- If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description.
+- You can use `screenshot` tools from "human" mcp server to capture screenshots and analyze the current issues with `eyes_analyze` tool.
+- Use multiple `scouter` agents to scout the current codebase or given codebase (if any) to understand the context, then report back to `copywriter` agent.
+- Use `copywriter` agent to write the enhanced copy into the code files, then report back to main agent.

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

@@ -0,0 +1,11 @@
+---
+description: Write creative & smart copy [FAST]
+---
+
+Write creative & smart copy for this user request:
+<user_request>$ARGUMENTS</user_request>
+
+## Workflow
+
+- If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description.
+- Use `copywriter` agent to write the copy, then report back to main agent.

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

@@ -0,0 +1,13 @@
+---
+description: Write good creative & smart copy [GOOD]
+---
+
+Write good creative & smart copy for this user request:
+<user_request>$ARGUMENTS</user_request>
+
+## Workflow
+
+- If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description.
+- Use multiple `researcher` agents in parallel to search for relevant information & multiple `scouter` agents to scout the current codebase or given codebase (if any) to understand the project, then report back to `planner` agent.
+- 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/.claude/commands/cook.md

@@ -0,0 +1,19 @@
+---
+description: Implement a feature
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+## Workflow:
+1. Use `planner` subagent and `researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
+2. Then use general agent (main agent) to implement the plan step by step.
+3. Run type checking and compile the code to make sure there are no syntax errors.
+4. Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
+5. Use `tester` subagent to 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 and 
+7. 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.
+8. 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 process until all tests pass.
+9. 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.
+10. If user approves the changes, use `docs-manager` subagent to update the docs if needed.
+11. Finally use `git-manager` subagent to commit and push to git repository.

package/.claude/commands/debug.md

@@ -0,0 +1,10 @@
+---
+description: Debugging technical issues and providing solutions.
+---
+ 
+**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.

package/.claude/commands/design/3d.md

@@ -0,0 +1,65 @@
+---
+description: Create immersive interactive 3D designs with Three.js
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
+<tasks>$ARGUMENTS</tasks>
+
+## Workflow:
+1. Use `ui-ux-designer` subagent and `researcher` subagent to create a comprehensive 3D design plan with TODO tasks in `./plans` directory.
+2. Then use `ui-ux-designer` subagent to implement the plan step by step.
+3. Create immersive 3D experiences using Three.js with particle effects, custom shaders, and interactive elements.
+4. Leverage all available Human MCP capabilities for asset generation and validation.
+5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
+
+## 3D Design Requirements:
+- Implement Three.js scenes with proper optimization
+- Create custom GLSL shaders for unique visual effects
+- Design GPU-accelerated particle systems
+- Add immersive camera controls and cinematic effects
+- Implement post-processing effects and render pipelines
+- Ensure responsive behavior across all devices
+- Optimize performance for real-time rendering
+- Add interactive elements and smooth animations
+
+## Human MCP Tools Integration:
+
+### Hands Tools (Image/Video Generation):
+- Generate textures, skyboxes, and environment maps with Gemini API
+- Create custom particle sprites and effect assets
+- Generate 3D object textures with specific styles
+- Create video backgrounds for immersive scenes
+- Apply camera movements for dynamic visual effects
+- Use inpainting/outpainting for seamless texture creation
+
+### JIMP Tools (Image Processing):
+- Process and optimize textures for WebGL
+- Create normal maps and height maps from images
+- Generate sprite sheets for particle systems
+- Remove backgrounds for transparent textures
+- Resize and optimize assets for performance
+- Apply masks for complex texture effects
+
+### Eyes Tools (Visual Analysis):
+- Analyze reference images for 3D scene composition
+- Compare design mockups with implementation
+- Validate texture quality and visual consistency
+- Extract color palettes from reference materials
+- Verify shader effects and visual output
+
+## Implementation Stack:
+- Three.js for 3D rendering
+- GLSL for custom vertex and fragment shaders
+- HTML/CSS/JS for UI integration
+- WebGL for GPU-accelerated graphics
+- Post-processing libraries for effects
+
+## Notes:
+- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them extensively to create realistic 3D assets.
+- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
+- Leverage Hands tools to create custom textures, particle sprites, environment maps, and visual effects.
+- Use JIMP tools to process and optimize all visual assets for WebGL performance.
+- Test 3D scenes across different devices and optimize for smooth 60fps performance.
+- Maintain and update `./docs/design-guideline.md` docs with 3D design patterns and shader libraries.
+- Document shader code, particle systems, and reusable 3D components for future reference.

package/.claude/commands/design/describe.md

@@ -0,0 +1,13 @@
+---
+description: Describe a design based on screenshot/video
+---
+
+Think hard to describe the design based on this screenshot/video: 
+<screenshot>$ARGUMENTS</screenshot>
+
+## Workflow:
+1. Use `eyes` analyze tool to describe super details of the screenshot/video so the developer can implement it easily.
+   - Be specific about design style, every element, elements' positions, every interaction, every animation, every transition, every color, every border, every icon, every font style, font size, font weight, every spacing, every padding, every margin, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every image, background transparency, etc.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
+2. Use `ui-ux-designer` subagent to create a design implementation plan of creating exactly the same result with the screenshot/video, break down the plan into TODO tasks in `./plans` directory.
+3. Report back to user with a summary of the plan.

package/.claude/commands/design/fast.md

@@ -0,0 +1,19 @@
+---
+description: Create a quick design
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+## Workflow:
+1. Use `ui-ux-designer` subagent and `researcher` subagent (research about design style, trends, fonts, colors, elements' positions, etc.) to create a design plan with TODO tasks in `./plans` directory.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
+2. Then use `ui-ux-designer` subagent to implement the plan step by step.
+3. If user doesn't specify, create the design in pure HTML/CSS/JS.
+4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+5. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
+
+## Notes:
+- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design and real assets.
+- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
+- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.claude/commands/design/good.md

@@ -0,0 +1,23 @@
+---
+description: Create an immersive design
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+## Workflow:
+1. Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan with TODO tasks in `./plans` directory.
+   - Research about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
+2. Then use `ui-ux-designer` subagent to implement the plan step by step.
+3. If user doesn't specify, create the design in pure HTML/CSS/JS.
+4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+5. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
+
+## Important Notes:
+- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
+- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
+- Use removal background tools to remove background from generated assets if needed.
+- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
+- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.claude/commands/design/screenshot.md

@@ -0,0 +1,23 @@
+---
+description: Create a design based on screenshot
+---
+
+Think hard to plan & start designing follow exactly this screenshot: 
+<screenshot>$ARGUMENTS</screenshot>
+
+## Workflow:
+1. Use `eyes` analyze tool to describe super details of the screenshot (design style, trends, fonts, colors, border, spacing, elements' positions, size, shape, texture, material, light, shadow, reflection, refraction, blur, glow, image, background transparency, transition, etc.)
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
+2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the screenshot, break down the plan into TODO tasks in `./plans` directory.
+3. Then implement the plan step by step.
+4. If user doesn't specify, create the design in pure HTML/CSS/JS.
+5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
+
+## Important Notes:
+- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
+- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
+- Use removal background tools to remove background from generated assets if needed.
+- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
+- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.claude/commands/design/video.md

@@ -0,0 +1,23 @@
+---
+description: Create a design based on video
+---
+
+Think hard to plan & start designing follow exactly this video: 
+<video>$ARGUMENTS</video>
+
+## Workflow:
+1. Use `eyes` analyze tool to describe super details of the video: be specific about describing every element, every interaction, every animation, every transition, every color, every font, every border, every spacing, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every image, background transparency, etc.
+   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given video, don't just use Inter or Poppins.
+2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the video, break down the plan into TODO tasks in `./plans` directory.
+3. Then implement the plan step by step.
+4. If user doesn't specify, create the design in pure HTML/CSS/JS.
+5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
+
+## Important Notes:
+- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
+- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
+- Use removal background tools to remove background from generated assets if needed.
+- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
+- Maintain and update `./docs/design-guideline.md` docs if needed.

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

@@ -0,0 +1,13 @@
+---
+description: Analyze the codebase and create initial documentation
+---
+
+Use `docs/` directory as the source of truth for documentation.
+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
+
+**IMPORTANT**: **Do not** start implementing.

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

@@ -0,0 +1,10 @@
+---
+description: Analyze the codebase and update documentation
+---
+
+Use `docs-manager` agent to analyze the codebase and update `docs/codebase-summary.md`
+
+## Notes:
+- Use `docs/` directory as the source of truth for documentation.
+
+**IMPORTANT**: **Do not** start implementing.

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

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

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

@@ -0,0 +1,11 @@
+---
+description: Analyze Github Actions logs and fix issues
+---
+## Github Actions URL
+<url>$ARGUMENTS</url>
+
+## Workflow
+- Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
+- Use proper developer agents to implement the plan.
+- Use `tester` agent to run the tests, 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.

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

@@ -0,0 +1,12 @@
+---
+description: Analyze and fix the issue [FAST]
+---
+
+Analyze and fix this issue:
+<issue>$ARGUMENTS</issue>
+
+## Workflow
+
+- If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
+- Use `tester` agent to test the fix and 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.

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

@@ -0,0 +1,18 @@
+---
+description: Use subagents to plan and fix hard 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 `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
+
+1. Use `planner` subagent and `researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
+2. Then use general agent (main agent) to implement the plan step by step.
+3. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+4. 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 
+5. Repeat the process until all tests pass or no more issues are reported.
+6. 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.
+7. Report back to user with a summary of the changes and explain everything briefly.

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

@@ -0,0 +1,16 @@
+---
+description: Analyze logs and fix issues
+---
+
+Use `debugger` agent to analyze the `./logs.txt` file, identify root causes of any errors or issues and respond with a report and solution.
+So the main agent can fix them.
+
+## Rules
+
+- Use `debugger` agent to read and analyze the entire `./logs.txt` file
+- Identify all errors, warnings, and potential issues
+- Determine the root causes of each issue
+- Fix all identified problems systematically based on the report
+- Verify fixes by running appropriate commands
+- Re-analyze logs after fixes to ensure issues are resolved
+

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

@@ -0,0 +1,18 @@
+---
+description: Run test suite and fix issues
+---
+
+## Reported Issues:
+<issue>
+ $ARGUMENTS
+</issue>
+
+## Workflow:
+1. First use `tester` subagent to compile the code and fix all syntax errors if any.
+2. Then use `tester` subagent to run the tests.
+3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues.
+4. Then use `planner` subagent to create a implementation plan with TODO tasks in `./plans` directory.
+5. Then implement the plan step by step.
+6. Use `tester` subagent to run the tests after implementing the plan, make sure it works, then report back to main agent.
+7. After finishing, delegate to `code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
+8. Repeat this process until all tests pass and no more errors are reported.

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

@@ -0,0 +1,10 @@
+---
+description: Fix type errors
+---
+
+Run `bun run typecheck` 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/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/integrate/polar.md

@@ -0,0 +1,42 @@
+---
+description: Implement payment integration with Polar.sh
+---
+
+Think harder to 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>
+
+## Workflow:
+
+### Fullfill the request
+
+* If you don't have any questions, skip this step and go to `Planning` step.
+* If you have any questions, ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* Repeat this process until you have all the information you need to proceed.
+
+### Planning
+
+1. Use `planner` subagent to read the Polar.sh docs and create a implementation plan with TODO tasks in `./plans` directory.
+2. Ask user to review and approve the plan, if the user requests to change the plan, repeat the previous step until the user approves the plan.
+
+### Implementation
+
+1. When user approves the plan, use **general agent (main agent)** to implement the plan step by step.
+2. Run type checking and compile the code to make sure there are no syntax errors.
+
+### Testing & Code Review
+
+5. Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
+6. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+7. 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 
+8. 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.
+9.  When all tests pass, 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 process until all tests pass.
+10. When all 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.
+
+### Documentation
+
+11. If user approves the changes, use `docs-manager` subagent to update the docs if needed.
+
+### Final Report
+
+12. Report 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/plan/ci.md

@@ -0,0 +1,12 @@
+---
+description: Analyze Github Actions logs and provide a plan to fix the issues
+---
+## Github Actions URL
+ $ARGUMENTS
+
+Use the `planer-researcher` 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.