thanh-kit 2.5.4 → 2.5.6

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 .claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
-   python3 .claude/skills/ui-ux-pro-max/scripts/search.py "immersive 3d" --domain style
-   python3 .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 .claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
-   python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
-   python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
-   python3 .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

@@ -1,35 +0,0 @@
----
-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 .claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
-   python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
-   python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
-   python3 .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

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

@@ -1,34 +0,0 @@
----
-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/fix/ci.md

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

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

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

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

package/templates/commands/fix/parallel.md

@@ -1,54 +0,0 @@
----
-description: ⚡⚡ Analyze & fix issues with parallel fullstack-developer agents
-argument-hint: [issues]
----
-
-**Ultrathink parallel** to fix: <issues>$ARGUMENTS</issues>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-
-## Workflow
-
-### 1. Issue Analysis
-- Use `debugger` subagent to analyze root causes
-- Use `/scout:ext` to find related files
-- Categorize issues by scope/area (frontend, backend, auth, payments, etc.)
-- Identify dependencies between issues
-
-### 2. Parallel Fix Planning
-- Trigger `/plan:parallel <detailed-fix-instructions>` for parallel-executable fix plan
-- Wait for plan with dependency graph, execution strategy, file ownership matrix
-- Group independent fixes for parallel execution
-- Sequential fixes for dependent issues
-
-### 3. Parallel Fix Implementation
-- Read `plan.md` for dependency graph
-- Launch multiple `fullstack-developer` agents in PARALLEL for independent fixes
-  - Example: "Fix auth + Fix payments + Fix UI" → launch 3 agents simultaneously
-  - Pass phase file path: `{plan-dir}/phase-XX-*.md`
-  - Include environment info
-- Wait for all parallel fixes complete before dependent fixes
-- Sequential fixes: launch one agent at a time
-
-### 4. Testing
-- Use `tester` subagent for full test suite
-- NO fake data/mocks/cheats
-- Verify all issues resolved
-- If fail: use `debugger`, fix, repeat
-
-### 5. Code Review
-- Use `code-reviewer` for all changes
-- Verify fixes don't introduce regressions
-- 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 fixes from parallel phases
-- Verification status per issue
-- Ask to commit (use `git-manager` if yes)
-
-**Example:** Fix 1 (auth) + Fix 2 (payments) + Fix 3 (UI) → Launch 3 fullstack-developer agents → Wait → Fix 4 (integration) sequential

package/templates/commands/fix/test.md

@@ -1,20 +0,0 @@
----
-description: ⚡⚡ Run test suite and fix issues
-argument-hint: [issues]
----
-
-Analyze the skills catalog and activate the skills that are needed for the task during the process.
-
-## Reported Issues:
-<issues>$ARGUMENTS</issues>
-
-## Workflow:
-1. Use `tester` subagent to compile the code and fix all syntax errors if any.
-2. Use `tester` subagent to run the tests and report back to main agent.
-3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then report back to main agent.
-4. Use `planner` subagent to create an implementation plan based on the reports, then report back to main agent.
-5. Use main agent to implement the plan step by step.
-6. Use `tester` agent to test the fix and make sure it works, then report back to main agent.
-6. Use `code-reviewer` subagent to quickly review the code changes and make sure it meets requirements, then report back to main agent.
-7. If there are issues or failed tests, repeat from step 2.
-8. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

package/templates/commands/fix/types.md

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

package/templates/commands/fix/ui.md

@@ -1,48 +0,0 @@
----
-description: ⚡⚡ Analyze and fix UI issues
-argument-hint: [issue]
----
-
-## Required Skills (Priority Order)
-1. **`ui-ux-pro-max`** - Design intelligence database (ALWAYS ACTIVATE FIRST)
-2. **`aesthetic`** - Design principles
-3. **`frontend-design`** - Implementation patterns
-
-Use `ui-ux-designer` subagent to read and analyze `./docs/design-guidelines.md` then fix the following issues:
-<issue>$ARGUMENTS</issue>
-
-## Workflow
-**FIRST**: Run `ui-ux-pro-max` searches to understand context and common issues:
-```bash
-python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<product-type>" --domain product
-python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<style-keywords>" --domain style
-python3 .claude/skills/ui-ux-pro-max/scripts/search.py "accessibility" --domain ux
-python3 .claude/skills/ui-ux-pro-max/scripts/search.py "z-index animation" --domain ux
-```
-
-If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
-
-1. Use `ui-ux-designer` subagent to implement the fix step by step.
-2. Use screenshot capture tools along with `ai-multimodal` skill to take screenshots of the implemented fix (at the exact parent container, don't take screenshot of the whole page) and use the appropriate Gemini analysis skills (`ai-multimodal`, `video-analysis`, or `document-extraction`) to analyze those outputs so the result matches the design guideline and addresses all issues.
-  - If the issues are not addressed, repeat the process until all issues are addressed.
-3. Use `chrome-devtools` skill to analyze the implemented fix and make sure it matches the design guideline.
-4. Use `tester` agent to test the fix and compile the code to make sure it works, then report back to main agent.
-  - If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.
-5. Project Management & Documentation:
-  **If user approves the changes:** Use `project-manager` and `docs-manager` subagents in parallel to update the project progress and documentation:
-    * Use `project-manager` subagent to update the project progress and task status in the given plan file.
-    * Use `docs-manager` subagent to update the docs in `./docs` directory if needed.
-    * Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
-    * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-  **If user rejects the changes:** Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
-6. Final Report:
-  * Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
-  * Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
-  * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-  * **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
-**REMEMBER**:
-- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
-- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
-- For image editing (removing background, adjusting, cropping), use `ImageMagick` skill or similar tools as needed.
-- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

package/templates/commands/fix.md

@@ -1,43 +0,0 @@
----
-description: ⚡⚡ Analyze and fix issues [INTELLIGENT ROUTING]
-argument-hint: [issues]
----
-
-**Analyze issues and route to specialized fix command:**
-<issues>$ARGUMENTS</issues>
-
-## Decision Tree
-
-**1. Check for existing plan:**
-- If markdown plan exists → `/code <path-to-plan>`
-
-**2. Route by issue type:**
-
-**A) Type Errors** (keywords: type, typescript, tsc, type error)
-→ `/fix:types`
-
-**B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
-→ `/fix:ui <detailed-description>`
-
-**C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
-→ `/fix:ci <github-actions-url-or-description>`
-
-**D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
-→ `/fix:test <detailed-description>`
-
-**E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
-→ `/fix:logs <detailed-description>`
-
-**F) Multiple Independent Issues** (2+ unrelated issues in different areas)
-→ `/fix:parallel <detailed-description>`
-
-**G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
-→ `/fix:hard <detailed-description>`
-
-**H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
-→ `/fix:fast <detailed-description>`
-
-## Notes
-- `detailed-description` = enhanced prompt describing issue in detail
-- If unclear, ask user for clarification before routing
-- Can combine routes: e.g., multiple type errors + UI issue → `/fix:parallel`

package/templates/commands/plan/ci.md

@@ -1,33 +0,0 @@
----
-description: Analyze Github Actions logs and provide a plan to fix the issues
-argument-hint: [github-actions-url]
----
-
-Activate `planning` skill.
-
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planner` subagent to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Plan File Specification:**
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P1
-  effort: {estimated fix time}
-  branch: {current git branch}
-  tags: [ci, bugfix]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.

package/templates/commands/plan/cro.md

@@ -1,69 +0,0 @@
----
-description: Create a CRO plan for the given content
-argument-hint: [issues]
----
-
-You are an expert in conversion optimization. Analyze the content based on the given issues:
-<issues>$ARGUMENTS</issues>
-
-Activate `planning` skill.
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-## Conversion Optimization Framework
-
-1. Headline 4-U Formula: **Useful, Unique, Urgent, Ultra-specific** (80% won't read past this)
-2. Above-Fold Value Proposition: Customer problem focus, no company story, zero scroll required
-3. CTA First-Person Psychology: "Get MY Guide" vs "Get YOUR Guide" (90% more clicks)
-4. 5-Field Form Maximum: Every field kills conversions, progressive profiling for the rest
-5. Message Match Precision: Ad copy, landing page headline, broken promises = bounce
-6. Social Proof Near CTAs: Testimonials with faces/names, results, placed at decision points
-7. Cognitive Bias Stack: Loss aversion (fear), social proof (FOMO), anchoring (pricing)
-8. PAS Copy Framework: Problem > Agitate > Solve, emotion before logic
-9. Genuine Urgency Only: Real deadlines, actual limits, fake timers destroy trust forever
-10. Price Anchoring Display: Show expensive option first, make real price feel like relief
-11. Trust Signal Clustering: Security badges, guarantees, policies all visible together
-12. Visual Hierarchy F-Pattern: Eyes scan F-shape, put conversions in the path
-13. Lead Magnet Hierarchy: Templates > Checklists > Guides (instant > delayed gratification)
-14. Objection Preemption: Address top 3 concerns before they think them, FAQ near CTA
-15. Mobile Thumb Zone: CTAs where thumbs naturally rest, not stretching required
-16. One-Variable Testing: Change one thing, measure impact, compound wins over time
-17. Post-Conversion Momentum: Thank you page sells next step while excitement peaks
-18. Cart Recovery Sequence: Email in 1 hour, retarget in 4 hours, incentive at 24 hours
-19. Reading Level Grade 6: Smart people prefer simple, 11-word sentences, short paragraphs
-20. TOFU/MOFU/BOFU Logic: Awareness content ≠ decision content, match intent precisely
-21. White Space = Focus: Empty space makes CTAs impossible to miss, crowded = confused
-22. Benefit-First Language: Features tell, benefits sell, transformations compel
-23. Micro-Commitment Ladder: Small yes leads to big yes, start with email only
-24. Performance Tracking Stack: Heatmaps show problems, recordings show why, events show what
-25. Weekly Optimization Ritual: Review metrics Monday, test Tuesday, iterate or scale
-
-## Workflow
-
-- If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure fullstack-developer can fully understand the issue easily based on the description.
-- If the user provides a URL, use `web_fetch` tool to fetch the content of the URL and analyze the current issues.
-- You can use screenshot capture tools along with `ai-multimodal` skill to capture screenshots of the exact parent container and analyze the current issues with the appropriate Gemini analysis skills (`ai-multimodal`, `gemini-video-understanding`, or `gemini-document-processing`).
-- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
-- Use `planner` agent to create a comprehensive CRO plan following the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Every `plan.md` MUST start with YAML frontmatter:
-    ```yaml
-    ---
-    title: "{Brief title}"
-    description: "{One sentence for card preview}"
-    status: pending
-    priority: P2
-    effort: {sum of phases, e.g., 4h}
-    branch: {current git branch}
-    tags: [cro, conversion]
-    created: {YYYY-MM-DD}
-    ---
-    ```
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-  - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-- Do not start implementing the CRO plan yet, wait for the user to approve the plan first.
-
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.