Name: creative
Author: ZVanoZ

Prompt file imported from ZVanoZ/dns-proxy-nodejs (.cursor/commands/creative.md). Copyright stays with the author.

CREATIVE Command - Design Decisions

This command performs structured design exploration for components flagged during planning.

Memory Bank Integration

Reads from:

memory-bank/tasks.md - Components requiring creative phases
memory-bank/activeContext.md - Current project context

Creates:

memory-bank/creative/creative-[feature_name].md - Design decision documents

Updates:

memory-bank/tasks.md - Records design decisions

Progressive Rule Loading

Step 1: Load Core Rules

Load: .cursor/rules/isolation_rules/main.mdc
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc

Step 2: Load CREATIVE Mode Map

Load: .cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc

Step 3: Load Creative Phase Enforcement

Load: .cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc
Load: .cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc

Step 4: Load Specialized Creative Rules (Lazy Loaded)

Load only when specific creative phase type is needed:

For Architecture Design:

Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc

For UI/UX Design:

Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-uiux.mdc

For Algorithm Design:

Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-algorithm.mdc

Workflow

Verify Planning Complete
- Check memory-bank/tasks.md for planning completion
- Verify creative phases are identified
- If not complete, return to /plan command
Identify Creative Phases
- Read components flagged for creative work from memory-bank/tasks.md
- Prioritize components for design exploration
Execute Creative Phase For each component:
- 🎨🎨🎨 ENTERING CREATIVE PHASE: [TYPE]
- Define requirements and constraints
- Generate 2-4 design options
- Analyze pros/cons of each option
- Select and justify recommended approach
- Document implementation guidelines
- Verify solution meets requirements
- 🎨🎨🎨 EXITING CREATIVE PHASE
Document Decisions
- Create memory-bank/creative/creative-[feature_name].md
- Update memory-bank/tasks.md with design decisions
Verify Completion
- Ensure all flagged components have completed creative phases
- Mark creative phase as complete in memory-bank/tasks.md

Usage

Type /creative to start creative design work for components flagged in the plan.

Next Steps

After all creative phases complete, proceed to /build command for implementation.

Install creative and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# CREATIVE Command - Design Decisions This command performs structured design exploration for components flagged during planning. ## Memory Bank Integration Reads from: - `memory-bank/tasks.md` - Components requiring creative phases - `memory-bank/activeContext.md` - Current project context Creates: - `memory-bank/creative/creative-[feature_name].md` - Design decision documents Updates: - `memory-bank/tasks.md` - Records design decisions ## Progressive Rule Loading ### Step 1: Load Core Rules ``` Load: .cursor/rules/isolation_rules/main.mdc Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc ``` ### Step 2: Load CREATIVE Mode Map ``` Load: .cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc ``` ### Step 3: Load Creative Phase Enforcement ``` Load: .cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc Load: .cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc ``` ### Step 4: Load Specialized Creative Rules (Lazy Loaded) Load only when specific creative phase type is needed: **For Architecture Design:** ``` Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc ``` **For UI/UX Design:** ``` Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-uiux.mdc ``` **For Algorithm Design:** ``` Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-algorithm.mdc ``` ## Workflow 1. **Verify Planning Complete** - Check `memory-bank/tasks.md` for planning completion - Verify creative phases are identified - If not complete, return to `/plan` command 2. **Identify Creative Phases** - Read components flagged for creative work from `memory-bank/tasks.md` - Prioritize components for design exploration 3. **Execute Creative Phase** For each component: - **🎨🎨🎨 ENTERING CREATIVE PHASE: [TYPE]** - Define requirements and constraints - Generate 2-4 design options - Analyze pros/cons of each option - Select and justify recommended approach - Document implementation guidelines - Verify solution meets requirements - **🎨🎨🎨 EXITING CREATIVE PHASE** 4. **Document Decisions** - Create `memory-bank/creative/creative-[feature_name].md` - Update `memory-bank/tasks.md` with design decisions 5. **Verify Completion** - Ensure all flagged components have completed creative phases - Mark creative phase as complete in `memory-bank/tasks.md` ## Usage Type `/creative` to start creative design work for components flagged in the plan. ## Next Steps After all creative phases complete, proceed to `/build` command for implementation.

{ "prompt": "# CREATIVE Command - Design Decisions\n\nThis command performs structured design exploration for components flagged during planning.\n\n## Memory Bank Integration\n\nReads from:\n- `memory-bank/tasks.md` - Components requiring creative phases\n- `memory-bank/activeContext.md` - Current project context\n\nCreates:\n- `memory-bank/creative/creative-[feature_name].md` - Design decision documents\n\nUpdates:\n- `memory-bank/tasks.md` - Records design decisions\n\n## Progressive Rule Loading\n\n### Step 1: Load Core Rules\n```\nLoad: .cursor/rules/isolation_rules/main.mdc\nLoad: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc\n```\n\n### Step 2: Load CREATIVE Mode Map\n```\nLoad: .cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc\n```\n\n### Step 3: Load Creative Phase Enforcement\n```\nLoad: .cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc\nLoad: .cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc\n```\n\n### Step 4: Load Specialized Creative Rules (Lazy Loaded)\nLoad only when specific creative phase type is needed:\n\n**For Architecture Design:**\n```\nLoad: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc\n```\n\n**For UI/UX Design:**\n```\nLoad: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-uiux.mdc\n```\n\n**For Algorithm Design:**\n```\nLoad: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-algorithm.mdc\n```\n\n## Workflow\n\n1. **Verify Planning Complete**\n - Check `memory-bank/tasks.md` for planning completion\n - Verify creative phases are identified\n - If not complete, return to `/plan` command\n\n2. **Identify Creative Phases**\n - Read components flagged for creative work from `memory-bank/tasks.md`\n - Prioritize components for design exploration\n\n3. **Execute Creative Phase**\n For each component:\n - **🎨🎨🎨 ENTERING CREATIVE PHASE: [TYPE]**\n - Define requirements and constraints\n - Generate 2-4 design options\n - Analyze pros/cons of each option\n - Select and justify recommended approach\n - Document implementation guidelines\n - Verify solution meets requirements\n - **🎨🎨🎨 EXITING CREATIVE PHASE**\n\n4. **Document Decisions**\n - Create `memory-bank/creative/creative-[feature_name].md`\n - Update `memory-bank/tasks.md` with design decisions\n\n5. **Verify Completion**\n - Ensure all flagged components have completed creative phases\n - Mark creative phase as complete in `memory-bank/tasks.md`\n\n## Usage\n\nType `/creative` to start creative design work for components flagged in the plan.\n\n## Next Steps\n\nAfter all creative phases complete, proceed to `/build` command for implementation.", "variables": [], "notes": "This command performs structured design exploration for components flagged during planning.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/ZVanoZ/dns-proxy-nodejs", "path": ".cursor/commands/creative.md", "ref": "5cfcc5e8ee541358b4c868549c22764742851576", "url": "https://github.com/ZVanoZ/dns-proxy-nodejs/blob/5cfcc5e8ee541358b4c868549c22764742851576/.cursor/commands/creative.md", "key": "ZVanoZ/dns-proxy-nodejs/.cursor/commands/creative.md" } } }

creative

About