thanh-kit 2.5.0

package/templates/commands/compact.md

@@ -0,0 +1,57 @@
+# Compact Context
+
+Proactively compress the current conversation context to optimize token usage.
+
+## When to Use
+
+- Before starting a new task in a long session
+- When working on multiple unrelated features
+- At natural workflow checkpoints (after commits, PR creation)
+- When context indicator shows high usage
+
+## Actions
+
+1. **Summarize completed work** - What was done, key decisions made
+2. **Preserve essential context** - Active file paths, current task, blockers
+3. **Clear redundant history** - Old exploration, superseded plans
+4. **Update memory** - Save important patterns to `.claude/memory/`
+
+## Best Practices
+
+- Use `/compact` at natural breakpoints, not mid-task
+- After compacting, briefly restate the current objective
+- Check that critical file paths are still accessible
+- If working on a bug, preserve error messages and stack traces
+
+## Context Preservation Checklist
+
+Before compacting, ensure you've saved:
+
+- [ ] Current branch and uncommitted changes status
+- [ ] Active file paths being modified
+- [ ] Any error messages or stack traces
+- [ ] Key decisions and their rationale
+- [ ] Pending items from todo list
+
+## Example Usage
+
+```
+User: /compact
+Claude: Compacting context...
+
+## Session Summary
+- Implemented employee export feature
+- Fixed validation bug in SaveEmployeeCommand
+- Created unit tests for EmployeeHelper
+
+## Active Context
+- Branch: feature/employee-export
+- Files: Employee.Application/Commands/ExportEmployees/
+- Current task: Add pagination to export
+
+## Cleared
+- Exploration of unrelated notification code
+- Superseded implementation approaches
+
+Ready to continue with pagination implementation.
+```

package/templates/commands/content/cro.md

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

package/templates/commands/content/enhance.md

@@ -0,0 +1,14 @@
+---
+description: Analyze the current copy issues and enhance it
+argument-hint: [issues]
+---
+
+Enhance the copy based on reported issues:
+<issues>$ARGUMENTS</issues>
+
+## Workflow
+
+- If the user provides screenshots, use `ai-multimodal` skill to analyze and describe the issues in detail, ensuring the copywriter understands the context.
+- If the user provides videos, use `ai-multimodal` (`video-analysis`) skill to analyze video content and extract relevant copy issues.
+- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+- Use `copywriter` agent to write the enhanced copy into the code files, then report back to main agent.

package/templates/commands/content/fast.md

@@ -0,0 +1,13 @@
+---
+description: Write creative & smart copy [FAST]
+argument-hint: [user-request]
+---
+
+Write creative & smart copy for this user request:
+<user_request>$ARGUMENTS</user_request>
+
+## Workflow
+
+- If the user provides screenshots, use `ai-multimodal` skill to analyze and describe the context.
+- If the user provides videos, use `ai-multimodal` (`video-analysis`) skill to analyze video content.
+- Use `copywriter` agent to write the copy, then report back to main agent.

package/templates/commands/content/good.md

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

package/templates/commands/context.md

@@ -0,0 +1,48 @@
+# Load Project Context
+
+Load current development context to help with subsequent tasks.
+
+## Git Status
+
+```bash
+git status --short
+git branch --show-current
+```
+
+## Recent Activity
+
+```bash
+# Recent commits
+git log --oneline -5
+
+# Uncommitted changes
+git diff --stat
+```
+
+## Project Structure Reminder
+
+**Backend Services:**
+- `TextSnippet` - Example application service
+- `Accounts` - Authentication & authorization
+
+**Frontend Apps (WebV2):**
+- `playground-text-snippet` - Example frontend application
+
+**Key Libraries:**
+- `platform-core` - Base components (PlatformComponent, stores)
+- `apps-domains` - Business domain (APIs, models, validators)
+- `platform-core` - UI components & utilities
+
+## Development Patterns
+
+**Backend:** Clean Architecture + CQRS + Entity Events
+**Frontend:** Angular 19 + Nx + PlatformVmStore
+
+## Current Session Focus
+
+Based on the git status, identify:
+- What files are being worked on
+- What feature/fix is in progress
+- Any uncommitted changes that need attention
+
+Summarize the current state to help with subsequent tasks.

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

@@ -0,0 +1,26 @@
+---
+description: ⚡ No research. Only scout, plan & implement ["trust me bro"]
+argument-hint: [tasks-or-prompt]
+---
+
+Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+**IMPORTANT**: Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+**Ensure token efficiency while maintaining high quality.**
+
+## Workflow:
+
+- **Scout**: Use `scout` subagent to find related resources, documents, and code snippets in the current codebase.
+- **Plan**: Trigger slash command `/plan:fast <detailed-instruction-prompt>` to create an implementation plan based on the reports from `scout` subagent.
+- **Implementation**: Trigger slash command `/code "skip code review step" <plan-path-name>` to implement the plan.

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

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

package/templates/commands/cook/auto.md

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

package/templates/commands/cook/fast.md

@@ -0,0 +1,47 @@
+---
+description: ⚡ Fast implementation - skip research, minimal planning
+argument-hint: [tasks]
+---
+
+Start working on these tasks immediately with minimal planning:
+<tasks>$ARGUMENTS</tasks>
+
+**Mode:** FAST - Skip research, minimal planning, trust your knowledge.
+
+## Workflow
+
+1. **Quick Planning** (skip research phase)
+   - Analyze task requirements directly
+   - Create minimal todo list with `TodoWrite`
+   - NO researcher subagents, NO scout commands
+
+2. **Rapid Implementation**
+   - Use `/code` directly on tasks
+   - Skip multi-step planning documents
+   - Focus on working code over documentation
+
+3. **Quick Validation**
+   - Run type-check and compile
+   - Manual spot-check over full test suite
+   - Skip code-reviewer subagent
+
+4. **Commit** (optional)
+   - Ask user if ready to commit via `AskUserQuestion`
+   - If yes, use `/git:cm`
+
+## When to Use
+
+- Simple features with clear requirements
+- Bug fixes with known solutions
+- Refactoring tasks
+- When user says "just do it"
+
+## Trade-offs
+
+| Aspect | Fast Mode | Full Mode |
+|--------|-----------|-----------|
+| Research | Skipped | Multiple agents |
+| Planning | Minimal | Full plan docs |
+| Testing | Quick check | Full test suite |
+| Review | Skipped | Code-reviewer |
+| Speed | ~2x faster | Thorough |

package/templates/commands/cook/hard.md

@@ -0,0 +1,80 @@
+---
+description: ⚡⚡⚡⚡ Thorough implementation with maximum verification
+argument-hint: [tasks]
+---
+
+**Ultrathink** to plan and implement these tasks with maximum verification:
+<tasks>$ARGUMENTS</tasks>
+
+**Mode:** HARD - Extra research, detailed planning, mandatory reviews.
+
+## Workflow
+
+### 1. Deep Research Phase
+- Launch 2-3 `researcher` subagents in parallel covering:
+  - Technical approach validation
+  - Edge cases and failure modes
+  - Security implications
+  - Performance considerations
+- Use `/scout:ext` for comprehensive codebase analysis
+- Generate research reports (max 150 lines each)
+
+### 2. Comprehensive Planning
+- Use `planner` subagent with all research reports
+- Create full plan directory with:
+  - `plan.md` - Overview with risk assessment
+  - `phase-XX-*.md` - Detailed phase files
+  - Success criteria for each phase
+  - Rollback strategy
+
+### 3. Verified Implementation
+- Implement one phase at a time
+- After each phase:
+  - Run type-check and compile
+  - Run relevant tests
+  - Self-review before proceeding
+
+### 4. Mandatory Testing
+- Use `tester` subagent for full test coverage
+- Write tests for:
+  - Happy path scenarios
+  - Edge cases from research
+  - Error handling paths
+- NO mocks or fake data allowed
+- Repeat until all tests pass
+
+### 5. Mandatory Code Review
+- Use `code-reviewer` subagent
+- Address all critical and major findings
+- Re-run tests after fixes
+- Repeat until approved
+
+### 6. Documentation Update
+- Use `docs-manager` to update relevant docs
+- Use `project-manager` to update project status
+- Record any architectural decisions
+
+### 7. Final Report
+- Summary of all changes
+- Test coverage metrics
+- Security considerations addressed
+- Unresolved questions (if any)
+- Ask user to review and approve
+
+## When to Use
+
+- Critical production features
+- Security-sensitive changes
+- Public API modifications
+- Database schema changes
+- Cross-service integrations
+
+## Quality Gates
+
+| Gate | Criteria |
+|------|----------|
+| Research | 2+ researcher reports |
+| Planning | Full plan directory |
+| Tests | All pass, no mocks |
+| Review | 0 critical/major findings |
+| Docs | Updated if needed |

package/templates/commands/cook/parallel.md

@@ -0,0 +1,90 @@
+---
+description: ⚡⚡⚡ Parallel implementation - multiple tasks simultaneously
+argument-hint: [tasks]
+---
+
+Execute these tasks in parallel for maximum efficiency:
+<tasks>$ARGUMENTS</tasks>
+
+**Mode:** PARALLEL - Multiple subagents working concurrently.
+
+## Workflow
+
+### 1. Task Decomposition
+- Analyze tasks for independence
+- Group into parallelizable work units
+- Identify dependencies between units
+- Create dependency graph
+
+### 2. Parallel Research (if needed)
+Launch multiple `researcher` subagents simultaneously:
+```
+Task A research ──┐
+Task B research ──┼──► Synthesis
+Task C research ──┘
+```
+
+### 3. Parallel Planning
+- Use `planner` subagent with synthesized research
+- Create plan with parallel-safe phases
+- Mark file ownership boundaries (prevent conflicts)
+
+### 4. Parallel Implementation
+Launch multiple `fullstack-developer` subagents:
+```
+Phase 1 (Backend API) ──┐
+Phase 2 (Frontend UI) ──┼──► Integration
+Phase 3 (Tests)       ──┘
+```
+
+**Critical:** Each subagent must stay within file ownership boundaries.
+
+### 5. Integration & Testing
+- Merge parallel outputs
+- Use `tester` subagent for integration tests
+- Use `debugger` if integration issues found
+
+### 6. Review & Report
+- Use `code-reviewer` for final review
+- Consolidate all changes
+- Report to user
+
+## Parallelization Rules
+
+| Rule | Description |
+|------|-------------|
+| **File Ownership** | Each subagent owns specific files - no overlap |
+| **Dependency Order** | Respect dependency graph |
+| **Max Concurrent** | 3 subagents max to prevent conflicts |
+| **Sync Points** | Integration checkpoints between phases |
+
+## When to Use
+
+- Multi-component features (backend + frontend)
+- Large refactoring across independent modules
+- Parallel test writing
+- Documentation updates alongside code
+
+## Example Task Split
+
+```
+"Add user authentication with login UI"
+├── Backend API (subagent 1)
+│   ├── auth-controller.ts
+│   └── auth-service.ts
+├── Frontend UI (subagent 2)
+│   ├── login-page.component.ts
+│   └── login-form.component.ts
+└── Tests (subagent 3)
+    ├── auth.spec.ts
+    └── login.e2e.ts
+```
+
+## Trade-offs
+
+| Aspect | Parallel | Sequential |
+|--------|----------|------------|
+| Speed | ~2-3x faster | Baseline |
+| Coordination | Higher complexity | Simple |
+| Conflicts | Risk of merge issues | None |
+| Context | Split across agents | Unified |

package/templates/commands/cook.md

@@ -0,0 +1,105 @@
+---
+description: ⚡⚡⚡ Implement a feature [step by step]
+argument-hint: [tasks]
+---
+
+Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+---
+
+## Your Approach
+
+1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Use `AskUserQuestion` tool to ask the user for their preferences.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+### Fullfill the request
+
+* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* Ask 1 question at a time, wait for the user to answer before moving to the next question.
+* If you don't have any questions, start the next step.
+
+**IMPORTANT:** Analyze the list of skills  at `.claude/skills/*` and intelligently activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use multiple `researcher` subagents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+
+### Plan
+
+*. Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an implementation plan using the progressive disclosure structure:
+  - Create a directory using naming pattern from `## Naming` section.
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+
+### Implementation
+
+* Use `/code` Slash Command to implement the plan step by step, follow the implementation plan in `./plans` directory.
+* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `ai-multimodal` skill to generate image assets.
+  * Use `ai-multimodal` skill to analyze and verify generated assets.
+  * Use `media-processing` skill for image editing (crop, resize, remove background) if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, **make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, tests should be real and cover all possible cases.
+* Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
+
+### Code Review
+
+* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. 
+* Repeat the "Testing" process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Project Management & Documentation
+
+**If user approves the changes:**
+* Use `project-manager` and `docs-manager` subagents in parallel to update the project progress and documentation:
+  * Use `project-manager` subagent to update the project progress and task status in the given plan file.
+  * Use `docs-manager` subagent to update the docs in `./docs` directory if needed.
+  * Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+**If user rejects the changes:**
+* Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
+
+### Onboarding
+
+* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
+* Help the user to configure (if needed) step by step, ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**REMEMBER**:
+- 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.

package/templates/commands/create-feature.md

@@ -0,0 +1,48 @@
+---
+description: Scaffold a new feature with backend and frontend components
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep, TodoWrite, Task
+---
+
+Create a new feature: $ARGUMENTS
+
+## Steps:
+
+1. **Analyze Requirements**
+   - Break down the feature requirements
+   - Identify the scope (backend only, frontend only, or full-stack)
+
+2. **Identify Service Location**
+   - Determine the appropriate microservice for backend
+   - Identify the Angular app/module for frontend
+
+3. **Plan Implementation**
+   - Domain entities needed
+   - CQRS Commands/Queries
+   - API endpoints (controllers)
+   - Angular components and services
+   - DTOs and validation
+
+4. **Use Platform Patterns**
+   - Reference patterns from CLAUDE.md
+   - Use `.github/prompts/` templates for scaffolding:
+     - `create-cqrs-command.prompt.md`
+     - `create-cqrs-query.prompt.md`
+     - `create-entity-event.prompt.md`
+     - `create-angular-component.prompt.md`
+     - `create-api-service.prompt.md`
+
+5. **Wait for Approval**
+   - Present the implementation plan
+   - **DO NOT proceed without explicit approval**
+
+6. **Create Files (After Approval)**
+   Execute in this order:
+   1. Domain entities (`.Domain/Entities/`)
+   2. Application layer (`.Application/UseCaseCommands/`, `.Application/UseCaseQueries/`)
+   3. Entity DTOs (`.Application/EntityDtos/`)
+   4. API controllers (`.Api/Controllers/`)
+   5. Frontend components and services
+
+7. **Verify**
+   - Build backend: `dotnet build`
+   - Build frontend: `nx build <app-name>`