thanh-kit 2.5.1 → 2.5.2

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

@@ -1,26 +0,0 @@
----
-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

@@ -1,49 +0,0 @@
----
-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

@@ -1,15 +0,0 @@
----
-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

@@ -1,47 +0,0 @@
----
-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

@@ -1,80 +0,0 @@
----
-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

@@ -1,90 +0,0 @@
----
-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

@@ -1,105 +0,0 @@
----
-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

@@ -1,48 +0,0 @@
----
-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>`

package/templates/commands/db-migrate.md

@@ -1,52 +0,0 @@
----
-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

@@ -1,13 +0,0 @@
----
-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

@@ -1,83 +0,0 @@
----
-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

@@ -1,23 +0,0 @@
----
-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

@@ -1,31 +0,0 @@
----
-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.