thanh-kit 2.5.0

package/templates/commands/db-migrate.md

@@ -0,0 +1,52 @@
+---
+description: Run or create database migrations
+allowed-tools: Bash, Read, Write, Edit, Glob, TodoWrite
+---
+
+Database migration: $ARGUMENTS
+
+## Instructions
+
+1. **Parse arguments**:
+   - `add <name>` → Create new EF Core migration
+   - `update` → Apply pending migrations
+   - `list` → List all migrations and status
+   - `rollback` → Revert last migration
+   - No argument → Show migration status
+
+2. **Identify database provider** from project:
+   - SQL Server: `PlatformExampleApp.TextSnippet.Persistence`
+   - PostgreSQL: `PlatformExampleApp.TextSnippet.Persistence.PostgreSql`
+   - MongoDB: Uses `PlatformMongoMigrationExecutor` (code-based)
+
+3. **For EF Core (SQL Server/PostgreSQL)**:
+
+   Add migration:
+
+   ```bash
+   cd src/PlatformExampleApp/PlatformExampleApp.TextSnippet.Persistence
+   dotnet ef migrations add <MigrationName> --startup-project ../PlatformExampleApp.TextSnippet.Api
+   ```
+
+   Update database:
+
+   ```bash
+   dotnet ef database update --startup-project ../PlatformExampleApp.TextSnippet.Api
+   ```
+
+   List migrations:
+
+   ```bash
+   dotnet ef migrations list --startup-project ../PlatformExampleApp.TextSnippet.Api
+   ```
+
+4. **For MongoDB migrations**:
+   - MongoDB uses code-based migrations via `PlatformMongoMigrationExecutor`
+   - Location: `*.Persistence.Mongo/Migrations/`
+   - Migrations run automatically on application startup
+   - To create: Generate new migration class following existing patterns
+
+5. **Safety checks**:
+   - Warn before applying migrations to production
+   - Show what changes will be applied
+   - Recommend backup before destructive operations

package/templates/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/commands/design/3d.md

@@ -0,0 +1,83 @@
+---
+description: Create immersive interactive 3D designs with Three.js
+argument-hint: [tasks]
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
+<tasks>$ARGUMENTS</tasks>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`threejs`** - Three.js/WebGL expertise
+3. **`frontend-design`** - Implementation patterns
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+0. **FIRST**: Run `ui-ux-pro-max` searches for 3D design context:
+   ```bash
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "immersive 3d" --domain style
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "animation" --domain ux
+   ```
+1. Use `ui-ux-designer` subagent and `researcher` subagent to create a comprehensive 3D design plan following the progressive disclosure structure:
+   - Create a directory using naming pattern from `## Naming` section.
+   - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+   - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+   - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+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 Gemini skills (ai-multimodal, ai-multimodal) 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-guidelines.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
+
+## Gemini Skills Integration:
+
+### ai-multimodal Skills & ImageMagick Skill (Asset Generation & Processing):
+- Generate textures, skyboxes, and environment maps with ai-multimodal skills
+- Create custom particle sprites and effect assets via ai-multimodal prompts
+- Generate 3D object textures with specific styles using ai-multimodal skills
+- Create video backgrounds for immersive scenes with ai-multimodal capabilities
+- Apply camera movements, inpainting, and outpainting through ai-multimodal skills
+- Refine, batch edit, and optimize outputs with imagemagick skill workflows
+
+### ImageMagick Skill (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 ai-multimodal skill. Use them extensively to create realistic 3D assets.
+- Always review, analyze and double check generated assets with ai-multimodal skill.
+- Leverage ai-multimodal skills and imagemagick skill to create custom textures, particle sprites, environment maps, and visual effects.
+- Use imagemagick skill 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-guidelines.md` docs with 3D design patterns and shader libraries.
+- Document shader code, particle systems, and reusable 3D components for future reference.

package/templates/commands/design/describe.md

@@ -0,0 +1,23 @@
+---
+description: Describe a design based on screenshot/video
+argument-hint: [screenshot]
+---
+
+Think hard to describe the design based on this screenshot/video: 
+<screenshot>$ARGUMENTS</screenshot>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`frontend-design`** - Visual analysis
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. Use `ai-multimodal` skills 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 following the progressive disclosure structure so the result matches the screenshot/video:
+   - 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).
+3. Report back to user with a summary of the plan.

package/templates/commands/design/fast.md

@@ -0,0 +1,31 @@
+---
+description: Create a quick design
+argument-hint: [tasks]
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`frontend-design`** - Quick implementation
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. **FIRST**: Run `ui-ux-pro-max` searches to gather design intelligence:
+   ```bash
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<industry>" --domain color
+   ```
+2. Use `ui-ux-designer` subagent to start the design process.
+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-guidelines.md` docs if needed.
+
+## Notes:
+- Remember that you have the capability to generate images, videos, edit images, etc. with `ai-multimodal` skills. Use them to create the design and real assets.
+- Always review, analyze and double check generated assets with `ai-multimodal` skills to verify quality.
+- Maintain and update `./docs/design-guidelines.md` docs if needed.

package/templates/commands/design/good.md

@@ -0,0 +1,35 @@
+---
+description: Create an immersive design
+argument-hint: [tasks]
+---
+
+Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`frontend-design`** - Screenshot analysis and design replication
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. **FIRST**: Run `ui-ux-pro-max` searches to gather design intelligence:
+   ```bash
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
+   python3 $HOME/.claude/skills/ui-ux-pro-max/scripts/search.py "<industry>" --domain color
+   ```
+2. Use `researcher` subagent to research about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
+3. Use `ui-ux-designer` subagent to implement the design step by step based on the research.
+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-guidelines.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 `ai-multimodal` skills for image generation. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with `ai-multimodal` skills to verify quality.
+- 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-guidelines.md` docs if needed.

package/templates/commands/design/screenshot.md

@@ -0,0 +1,34 @@
+---
+description: Create a design based on screenshot
+argument-hint: [screenshot]
+---
+
+Think hard to plan & start designing follow exactly this screenshot: 
+<screenshot>$ARGUMENTS</screenshot>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`frontend-design`** - Screenshot analysis and replication
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. Use `ai-multimodal` skills 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 following the progressive disclosure structure so the final result matches the screenshot:
+   - 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).
+   - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+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-guidelines.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 ai-multimodal skill for image generation. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with ai-multimodal skill to verify quality.
+- 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-guidelines.md` docs if needed.

package/templates/commands/design/video.md

@@ -0,0 +1,34 @@
+---
+description: Create a design based on video
+argument-hint: [video]
+---
+
+Think hard to plan & start designing follow exactly this video: 
+<video>$ARGUMENTS</video>
+
+## Required Skills (Priority Order)
+1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
+2. **`frontend-design`** - Video analysis and replication
+
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+1. Use `ai-multimodal` skills 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 following the progressive disclosure structure so the final result matches the video:
+   - 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).
+   - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+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-guidelines.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 ai-multimodal skill for image generation. Use them to create the design with real assets.
+- Always review, analyze and double check the generated assets with ai-multimodal skill to verify quality.
+- 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-guidelines.md` docs if needed.

package/templates/commands/docs/init.md

@@ -0,0 +1,39 @@
+---
+description: ⚡⚡⚡⚡ Analyze the codebase and create initial documentation
+---
+
+## Phase 1: Parallel Codebase Scouting
+
+**You (main agent) must spawn scouts** - subagents cannot spawn subagents.
+
+1. Run `ls -la` to identify actual project directories
+2. Spawn 2-4 `scout-external` (preferred, uses Gemini 2M context) or `scout` (fallback) via Task tool
+3. Target directories **that actually exist** - adapt to project structure, don't hardcode paths
+4. Merge scout results into context summary
+
+## 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.
+
+## [CRITICAL] Code Evidence Requirements
+
+All documentation MUST follow evidence rules from `.claude/skills/feature-docs/SKILL.md` → `[CRITICAL] MANDATORY CODE EVIDENCE RULE`
+
+### Quick Reference
+- **Format**: `**Evidence**: {FilePath}:{LineNumber}`
+- **Status**: ✅ Verified / ⚠️ Stale / ❌ Missing
+- **Verification**: 3-pass verification required before completion
+
+### Evidence Verification Table (Required)
+| Entity/Component | Documented Lines | Actual Lines | Status |
+|------------------|------------------|--------------|--------|
+| `Entity.cs` | L6-15 | L6-15 | ✅ Verified |
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/commands/docs/summarize.md

@@ -0,0 +1,31 @@
+---
+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>
+
+## [CRITICAL] Code Evidence Requirements
+
+All documentation summaries MUST follow evidence rules from `.claude/skills/feature-docs/SKILL.md` → `[CRITICAL] MANDATORY CODE EVIDENCE RULE`
+
+### Quick Reference
+- **Format**: `**Evidence**: {FilePath}:{LineNumber}`
+- **Status**: ✅ Verified / ⚠️ Stale / ❌ Missing
+- **Requirement**: Maintain evidence links when summarizing
+
+## 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/commands/docs/update.md

@@ -0,0 +1,57 @@
+---
+description: ⚡⚡⚡ Analyze the codebase and update documentation
+---
+
+## Phase 1: Parallel Codebase Scouting
+
+**You (main agent) must spawn scouts** - subagents cannot spawn subagents.
+
+1. Run `ls -la` to identify actual project directories
+2. Spawn 2-4 `scout-external` (preferred, uses Gemini 2M context) or `scout` (fallback) via Task tool
+3. Target directories **that actually exist** - adapt to project structure, don't hardcode paths
+4. Merge scout results into context summary
+
+## 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>
+
+## [CRITICAL] Code Evidence Requirements
+
+All documentation MUST follow evidence rules from `.claude/skills/feature-docs/SKILL.md` → `[CRITICAL] MANDATORY CODE EVIDENCE RULE`
+
+### Quick Reference
+- **Format**: `**Evidence**: {FilePath}:{LineNumber}`
+- **Status**: ✅ Verified / ⚠️ Stale / ❌ Missing
+- **Verification**: 3-pass verification required before completion
+
+### Stale Evidence Detection
+
+When updating documentation:
+1. **Read actual source files** at claimed line numbers
+2. **Verify evidence matches** documented behavior
+3. **Update stale references** - mark with ⚠️ if line numbers changed
+4. **Refresh line numbers** after code changes
+
+### Evidence Verification Table (Required)
+| Entity/Component | Documented Lines | Actual Lines | Status |
+|------------------|------------------|--------------|--------|
+| `Entity.cs` | L6-15 | L6-15 | ✅ Verified |
+| `Handler.cs` | L45-60 | L52-67 | ⚠️ Stale |
+
+## Important
+- Use `docs/` directory as the source of truth for documentation.
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/commands/feature.md

@@ -0,0 +1,62 @@
+# Implement Feature: $ARGUMENTS
+
+Implement a new feature following EasyPlatform development workflow.
+
+## Phase 1: Understanding
+
+1. **Parse feature requirements** from: $ARGUMENTS
+2. **Identify affected services:**
+   - TextSnippet (Example)
+   - TextSnippet (Example)
+   - TextSnippet (Example)
+   - TextSnippet (Example)
+
+3. **Search for similar implementations:**
+   - Find existing patterns in the codebase
+   - Identify reusable components
+
+## Phase 2: Design
+
+1. **Plan the implementation:**
+   - Backend: Domain entities, Commands/Queries, Event handlers
+   - Frontend: Components, Stores, API services
+   - Database: Migrations if needed
+
+2. **Identify file locations:**
+   ```
+   Backend:
+   - src/PlatformExampleApp/{Service}/{Service}.Domain/Entities/
+   - src/PlatformExampleApp/{Service}/{Service}.Application/UseCaseCommands/
+   - src/PlatformExampleApp/{Service}/{Service}.Application/UseCaseQueries/
+   - src/PlatformExampleApp/{Service}/{Service}.Application/UseCaseEvents/
+
+   Frontend (WebV2):
+   - src/PlatformExampleAppWeb/apps/{app}/src/app/features/
+   - src/PlatformExampleAppWeb/libs/apps-domains/src/{domain}/
+   ```
+
+## Phase 3: Create Implementation Plan
+
+Present a detailed plan with:
+- List of files to create/modify
+- Order of implementation
+- Dependencies between components
+- Test strategy
+
+## Phase 4: Wait for Approval
+
+**CRITICAL:** Wait for explicit user approval before writing any code.
+
+## Phase 5: Implementation
+
+After approval:
+1. Create entities/DTOs
+2. Create Commands/Queries with handlers
+3. Create event handlers for side effects
+4. Create frontend components
+5. Add tests
+
+Use appropriate skills:
+- `backend-cqrs-command` for commands
+- `backend-cqrs-query` for queries
+- `frontend-angular-component` for UI

package/templates/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/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. Activate `debugging` skills and `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/templates/commands/fix/hard.md

@@ -0,0 +1,39 @@
+---
+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.
+
+### 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**:
+- 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/templates/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.