cokit-cli 1.0.8 → 1.0.9

package/prompts/ck-code-auto.prompt.md

@@ -1,172 +0,0 @@
----
-agent: 'agent'
-description: '[AUTO] Start coding & testing an existing plan ("trust me bro")'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**MUST READ** `CLAUDE.md` then **THINK HARDER** to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<plan>${input}</plan>
-
-## Arguments
-- $PLAN: $1 (Mention specific plan or auto detected, default: latest plan)
-- $ALL_PHASES: $2 (`Yest` to finish all phases in one run or `No` to implement phase-by-phase and wait for confirmation, default is `Yes`)
-
----
-
-## Role Responsibilities
-- You are a senior software engineer who must study the provided implementation plan end-to-end before writing code.
-- Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution.
-- Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring **YAGNI**, **KISS**, and **DRY** principles.
-
-**IMPORTANT:** Remind these rules with  communication:
-- Sacrifice grammar for the sake of concision when writing reports.
-- In reports, list any unresolved questions at the end, if any.
-- Ensure token efficiency while maintaining high quality.
-
----
-
-## Step 0: Plan Detection & Phase Selection
-
-**If `$PLAN` is empty:**
-1. Find latest `plan.md` in `.s` | `find .s -name "plan.md" -type f -exec stat -f "%m %N" {} \; 2>/dev/null | sort -rn | head -1 | cut -d' ' -f2-`
-2. Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned)
-
-**If `$PLAN` provided:** Use that plan and detect which phase to work on (auto-detect or use argument like "phase-2").
-
-**Output:** `✓ Step 0: [Plan Name] - [Phase Name]`
-
-** Pattern (use throughout):**
-```
-Task(_type="[type]", prompt="[task description]", description="[brief]")
-```
-
----
-
-## Workflow Sequence
-
-**Rules:** Follow steps 1-5 in order. Each step requires output marker starting with "✓ Step N:". Mark each complete in `TodoWrite` before proceeding. Do not skip steps.
-
----
-
-## Step 1: Analysis & Task Extraction
-read plan file completely. Map dependencies between tasks. List ambiguities or blockers. Identify required skills/tools and activate from catalog. Parse phase file and extract actionable tasks.
-
-**TodoWrite Initialization & Task Extraction:**
-`project-manager` agent must respond back with:
-- Initialize `TodoWrite` with `Step 0: [Plan Name] - [Phase Name]` and all command steps (Step 1 through Step 5)
-- Read phase file (e.g., phase-01-preparation.md)
-- Look for tasks/steps/phases/sections/numbered/bulleted lists
-- MUST convert to `TodoWrite` tasks:
-  - Phase Implementation tasks → Step 2.X (Step 2.1, Step 2.2, etc.)
-  - Phase Testing tasks → Step 3.X (Step 3.1, Step 3.2, etc.)
-  - Phase Code Review tasks → Step 4.X (Step 4.1, Step 4.2, etc.)
-- Ensure each task has UNIQUE name (increment X for each task)
-- Add tasks to `TodoWrite` after their corresponding command step
-
-**Output:** `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list or "none"]`
-
-Mark Step 1 complete in `TodoWrite`, mark Step 2 in_progress.
-
----
-
-## Step 2: Implementation
-
-Implement selected plan phase step-by-step following extracted tasks (Step 2.1, Step 2.2, etc.). Mark tasks complete as done. For UI work, /docs/design-guidelines.md". Use `ai-multimodal` skill for image assets, imagemagick in `media-processing` skill for editing. Run type checking and compile to verify no syntax errors.
-
-**Output:** `✓ Step 2: Implemented [N] files - [X/Y] tasks complete, compilation passed`
-
-Mark Step 2 complete in `TodoWrite`, mark Step 3 in_progress.
-
----
-
-## Step 3: Testing
-
-Write tests covering happy path, edge cases, and error cases.  If ANY tests fail: STOP,  Repeat until 100% pass.
-
-**Testing standards:** Unit tests may use mocks for external dependencies (APIs, DB). Integration tests use test environment. E2E tests use real but isolated data. Forbidden: commenting out tests, changing assertions to pass, TODO/FIXME to defer fixes.
-
-**Output:** `✓ Step 3: Tests [X/X passed] - All requirements met`
-
-**Validation:** If X ≠ total, Step 3 INCOMPLETE - do not proceed.
-
-Mark Step 3 complete in `TodoWrite`, mark Step 4 in_progress.
-
----
-
-## Step 4: Code Review
-
- Check security, performance, architecture, YAGNI/KISS/DRY". If critical issues found: **STOP**, fix all, re-run `tester` to verify, re-run `code-reviewer`. Repeat until no critical issues.
-
-**Critical issues:** Security vulnerabilities (XSS, SQL injection, OWASP), performance bottlenecks, architectural violations, principle violations.
-
-**Output:** `✓ Step 4: Code reviewed - [0] critical issues`
-
-**Validation:** If critical issues > 0, Step 4 INCOMPLETE - do not proceed.
-
-Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
-
----
-
-## Step 5: Finalize
-
-1. **STATUS UPDATE - BOTH MANDATORY - PARALLEL EXECUTION:**
-- **Call** `project-manager` sub-agent: "Update plan status in [plan-path]. Mark plan phase [phase-name] as DONE with timestamp. Update roadmap."
-- **Call** `docs-manager` sub-agent: "Update docs for plan phase [phase-name]. Changed files: [list]."
-
-2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
-- If this is the last phase: ask if user wants to set up onboarding requirements.
-
-3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- **Call**  to handle git operation.
-- Run only if: Steps 1 and 2 successful + Tests passed
-- Auto-stage, commit with message [phase - plan] to LOCAL repository only
-- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-
-**Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
-
-Mark Step 5 complete in `TodoWrite`.
-
-**Important:**
-If $ALL_PHASES is `Yes`, proceed to the next phase automatically.
-If $ALL_PHASES is `No`, wait for user confirmation before proceeding to the next phase:
-- Ask if user wants to proceed to the next phase: "**Phase workflow finished. Ready for next plan phase.**"
-
-## Summary report
-If this is the last phase, generate a concise summary report.
-Ask these questions:
-- If user wants to preview the report with `/preview` .
-- If user wants to archive the plan with :archive` .
-
----
-
-## Critical Enforcement Rules
-
-**Step outputs must follow unified format:** `✓ Step [N]: [Brief status] - [Key metrics]`
-
-**Examples:**
-- Step 0: `✓ Step 0: [Plan Name] - [Phase Name]`
-- Step 1: `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list]`
-- Step 2: `✓ Step 2: Implemented [N] files - [X/Y] tasks complete`
-- Step 3: `✓ Step 3: Tests [X/X passed] - All requirements met`
-- Step 4: `✓ Step 4: Code reviewed - [0] critical issues`
-- Step 5: `✓ Step 5: Finalize - Status updated - Git committed`
-
-**If any "✓ Step N:" output missing, that step is INCOMPLETE.**
-
-**TodoWrite tracking required:** Initialize at Step 0, mark each step complete before next.
-
-**Mandatory  calls:**
-- Step 3: `tester`
-- Step 4: `code-reviewer`
-- Step 5: `project-manager` AND `docs-manager` AND `git-manager`
-
-**Blocking gates:**
-- Step 3: Tests must be 100% passing
-- Step 4: Critical issues must be 0
-
-**REMEMBER:**
-- Do not skip steps. Do not proceed if validation fails.
-- One plan phase per command run. Command focuses on single plan phase only.
-- 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/prompts/ck-code-no-test.prompt.md

@@ -1,160 +0,0 @@
----
-agent: 'agent'
-description: 'Start coding an existing plan (no testing)'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**MUST READ** `CLAUDE.md` then **THINK HARDER** to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<plan>${input}</plan>
-
----
-
-## Role Responsibilities
-- You are a senior software engineer who must study the provided implementation plan end-to-end before writing code.
-- Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution.
-- Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring **YAGNI**, **KISS**, and **DRY** principles.
-
-**IMPORTANT:** Remind these rules with  communication:
-- Sacrifice grammar for the sake of concision when writing reports.
-- In reports, list any unresolved questions at the end, if any.
-- Ensure token efficiency while maintaining high quality.
-
----
-
-## Step 0: Plan Detection & Phase Selection
-
-**If `${input}` is empty:**
-1. Find latest `plan.md` in `.s` | `find .s -name "plan.md" -type f -exec stat -f "%m %N" {} \; 2>/dev/null | sort -rn | head -1 | cut -d' ' -f2-`
-2. Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned)
-
-**If `${input}` provided:** Use that plan and detect which phase to work on (auto-detect or use argument like "phase-2").
-
-**Output:** `✓ Step 0: [Plan Name] - [Phase Name]`
-
-** Pattern (use throughout):**
-```
-Task(_type="[type]", prompt="[task description]", description="[brief]")
-```
-
----
-
-## Workflow Sequence
-
-**Rules:** Follow steps 1-6 in order. Each step requires output marker starting with "✓ Step N:". Mark each complete in TodoWrite before proceeding. Do not skip steps.
-
----
-
-## Step 1: Analysis & Task Extraction
-
-Read plan file completely. Map dependencies between tasks. List ambiguities or blockers. Identify required skills/tools and activate from catalog. Parse phase file and extract actionable tasks.
-
-**TodoWrite Initialization & Task Extraction:**
-- Initialize TodoWrite with `Step 0: [Plan Name] - [Phase Name]` and all command steps (Step 1 through Step 6)
-- Read phase file (e.g., phase-01-preparation.md)
-- Look for tasks/steps/phases/sections/numbered/bulleted lists
-- MUST convert to TodoWrite tasks:
-  - Phase Implementation tasks → Step 2.X (Step 2.1, Step 2.2, etc.)
-  - Phase Code Review tasks → Step 3.X (Step 3.1, Step 3.2, etc.)
-- Ensure each task has UNIQUE name (increment X for each task)
-- Add tasks to TodoWrite after their corresponding command step
-
-**Output:** `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list or "none"]`
-
-Mark Step 1 complete in TodoWrite, mark Step 2 in_progress.
-
----
-
-## Step 2: Implementation
-
-Implement selected plan phase step-by-step following extracted tasks (Step 2.1, Step 2.2, etc.). Mark tasks complete as done. For UI work, /docs/design-guidelines.md". Use `ai-multimodal` skill for image assets, `imagemagick` for editing. Run type checking and compile to verify no syntax errors.
-
-**Output:** `✓ Step 2: Implemented [N] files - [X/Y] tasks complete, compilation passed`
-
-Mark Step 2 complete in TodoWrite, mark Step 3 in_progress.
-
----
-
-## Step 3: Code Review
-
- Check security, performance, architecture, YAGNI/KISS/DRY". If critical issues found: STOP, fix all, re-run `tester` to verify, re-run `code-reviewer`. Repeat until no critical issues.
-
-**Critical issues:** Security vulnerabilities (XSS, SQL injection, OWASP), performance bottlenecks, architectural violations, principle violations.
-
-**Output:** `✓ Step 3: Code reviewed - [0] critical issues`
-
-**Validation:** If critical issues > 0, Step 3 INCOMPLETE - do not proceed.
-
-Mark Step 3 complete in TodoWrite, mark Step 4 in_progress.
-
----
-
-## Step 4: User Approval ⏸ BLOCKING GATE
-
-Present summary (3-5 bullets): what implemented, code review outcome.
-
-**Ask user explicitly:** "Phase implementation complete. Code reviewed. Approve changes?"
-
-**Stop and wait** - do not output Step 5 content until user responds.
-
-**Output (while waiting):** `⏸ Step 4: WAITING for user approval`
-
-**Output (after approval):** `✓ Step 4: User approved - Ready to complete`
-
-Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
-
----
-
-## Step 5: Finalize
-
-**Prerequisites:** User approved in Step 4 (verified above).
-
-1. **STATUS UPDATE - BOTH MANDATORY - PARALLEL EXECUTION:**
-- **Call** `project-manager` sub-agent: "Update plan status in [plan-path]. Mark plan phase [phase-name] as DONE with timestamp. Update roadmap."
-- **Call** `docs-manager` sub-agent: "Update docs for plan phase [phase-name]. Changed files: [list]."
-
-2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
-
-3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- Run only if: Steps 1 and 2 successful + User approved
-- Auto-stage, commit with message [phase - plan] to LOCAL repository only
-- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-
-**Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
-
-Mark Step 5 complete in TodoWrite.
-
-**Phase workflow finished. Ready for next plan phase.**
-
----
-
-## Critical Enforcement Rules
-
-**Step outputs must follow unified format:** `✓ Step [N]: [Brief status] - [Key metrics]`
-
-**Examples:**
-- Step 0: `✓ Step 0: [Plan Name] - [Phase Name]`
-- Step 1: `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list]`
-- Step 2: `✓ Step 2: Implemented [N] files - [X/Y] tasks complete`
-- Step 3: `✓ Step 3: Code reviewed - [0] critical issues`
-- Step 4: `✓ Step 4: User approved - Ready to complete`
-- Step 5: `✓ Step 5: Finalize - Status updated - Git committed`
-
-**If any "✓ Step N:" output missing, that step is INCOMPLETE.**
-
-**TodoWrite tracking required:** Initialize at Step 0, mark each step complete before next.
-
-**Mandatory  calls:**
-- Step 3: `code-reviewer`
-- Step 4: `project-manager` AND `docs-manager` (when user approves)
-
-**Blocking gates:**
-- Step 3: Critical issues must be 0
-- Step 4: User must explicitly approve
-- Step 5: Both `project-manager` and `docs-manager` must complete successfully
-
-**REMEMBER:**
-- Do not skip steps. Do not proceed if validation fails. Do not assume approval without user response.
-- One plan phase per command run. Command focuses on single plan phase only.
-- 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 `media-processing` skill or similar tools as needed.

package/prompts/ck-code-parallel.prompt.md

@@ -1,57 +0,0 @@
----
-agent: 'agent'
-description: 'Execute parallel or sequential phases based on plan structure'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-Execute plan: <plan>${input}</plan>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-
-## Workflow
-
-### 1. Plan Analysis
-- Read `plan.md` from given path
-- **Check for:** Dependency graph, Execution strategy, Parallelization Info, File Ownership matrix
-- **Decision:** IF parallel-executable → Step 2A, ELSE → Step 2B
-
-### 2A. Parallel Execution
-1. Parse execution strategy (which phases concurrent/sequential, file ownership)
-2. Launch multiple `fullstack-developer` agents simultaneously for parallel phases
-   - Pass: phase file path, environment info, file ownership boundaries
-3. Wait for parallel group completion, verify no conflicts
-4. Execute sequential phases (one agent per phase after dependencies)
-5. Proceed to Step 3
-
-### 2B. Sequential Execution
-Follow :
-1. Use main agent step by step
-2. Read `plan.md`, implement phases one by one
-3. Use `project-manager` for progress updates
-4. Use `ui-ux-designer` for frontend
-5. Run type checking after each phase
-6. Proceed to Step 3
-
-### 3. Testing
-- Use `tester` for full suite (NO fake data/mocks)
-- If fail: `debugger` → fix → repeat
-
-### 4. Code Review
-- Use `code-reviewer` for all changes
-- If critical: fix → retest
-
-### 5. Project Management & Docs
-- If approved: `project-manager` + `docs-manager`  (update plans, docs, roadmap)
-- If rejected: fix → repeat
-
-### 6. Onboarding
-- Guide user step by step (1 question at a time)
-
-### 7. Final Report
-- Summary, guide, next steps
-- Ask to commit to LOCAL repository (use `git-manager` if yes)
-- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-
-**Examples:**
-- Parallel: "Phases 1-3 parallel, then 4" → Launch 3 agents → Wait → Launch 1 agent
-- Sequential: "Phase 1 → 2 → 3" → Main agent implements each phase

package/prompts/ck-coding-level.prompt.md

@@ -1,54 +0,0 @@
----
-agent: 'agent'
-description: 'Set your coding experience level for tailored explanations and output format.'
-tools: ['search/codebase']
----
-
-Set your coding experience level for tailored explanations and output format.
-
-## Usage
-
-`/coding-level [0-5]`
-
-## Levels
-
-| Level | Name | Description |
-|-------|------|-------------|
-| 0 | ELI5 | Zero coding experience - analogies, no jargon, step-by-step |
-| 1 | Junior | 0-2 years - concepts explained, WHY not just HOW |
-| 2 | Mid-Level | 3-5 years - design patterns, system thinking |
-| 3 | Senior | 5-8 years - trade-offs, business context, architecture |
-| 4 | Tech Lead | 8-10 years - risk assessment, business impact, strategy |
-| 5 | God Mode | Expert - default behavior, maximum efficiency (default) |
-
-## How It Works
-
-1. Set `codingLevel` in 
-2. Guidelines are **automatically injected** on every session start
-3. No manual activation needed - it just works!
-
-## Example
-
-Set level 1 in :
-```json
-{
-  "codingLevel": 1,
-  ...
-}
-```
-
-Next session, Claude will automatically:
-- Explain concepts and techniques clearly
-- Always explain WHY, not just HOW
-- Point out common mistakes
-- Add "Key Takeaways" after implementations
-
-## Optional: Manual Output Styles
-
-For finer control, you can also use `/output-style` with these styles:
-- `coding-level-0-eli5`
-- `coding-level-1-junior`
-- `coding-level-2-mid`
-- `coding-level-3-senior`
-- `coding-level-4-lead`
-- `coding-level-5-god`

package/prompts/ck-cook-auto-fast.prompt.md

@@ -1,26 +0,0 @@
----
-agent: 'agent'
-description: 'No research. Only scout, plan & implement ["trust me bro"]'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>${input}</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.
-
----
-
-**
-
-## Workflow:
-
-- **Scout**: find related resources, documents, and code snippets in the current codebase.
-- **Plan**: 
-- **Implementation**: 

package/prompts/ck-cook-auto-parallel.prompt.md

@@ -1,50 +0,0 @@
----
-agent: 'agent'
-description: 'Plan parallel phases & execute with fullstack-developer agents'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink parallel** to implement: <tasks>${input}</tasks>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-
-## Workflow
-
-### 1. Research (Optional)
-- Use max 2 `researcher` agents  if tasks complex
-- Use  to search codebase
-- Keep reports ≤150 lines
-
-### 2. Parallel Planning
-- Trigger :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  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
-- 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` 
-- 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 to LOCAL repository (use `git-manager` if yes)
-- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-
-**Example:** Phases 1-3 parallel → Launch 3 fullstack-developer agents → Wait → Phase 4 sequential

package/prompts/ck-cook-auto.prompt.md

@@ -1,17 +0,0 @@
----
-agent: 'agent'
-description: 'Implement a feature automatically ("trust me bro")'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink** to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>${input}</tasks>
-
-**
-
-## Workflow:
-1.
-2.
-3. Finally ask user if they want to commit to git repository, if yes trigger `/git:cm` to create a LOCAL commit only.
-
-**IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.

package/prompts/ck-design-3d.prompt.md

@@ -1,84 +0,0 @@
----
-agent: 'agent'
-description: 'Create immersive interactive 3D designs with Three.js'
-tools: ['search/codebase', 'web/fetch', 'web/githubRepo']
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>${input}</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  "<product-type>" --domain product
-   python3  "immersive 3d" --domain style
-   python3  "animation" --domain ux
-   ```
-1. 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 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/prompts/ck-design-describe.prompt.md

@@ -1,24 +0,0 @@
----
-agent: 'agent'
-description: 'Describe a design based on screenshot/video'
-tools: ['search/codebase', 'web/fetch']
----
-
-Think hard to describe the design based on this screenshot/video:
-<screenshot>${input}</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. 
-   - 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. 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.