Check for .continue-here.md existence to determine mode. If present, update state files. If absent, skip state updates.
How would you like to start the UI design?
- Start from aesthetic template - Apply saved visual system
- Start from scratch - Create custom design
- List all aesthetics - Browse library before deciding
Choose (1-3): _
See references/aesthetic-integration.md for complete integration details.
Include in invocation prompt:
- All gathered requirements (layout, controls, colors, etc.)
- Quality expectation: "Design must look like commercial $50-200 audio plugin - intentional decisions, not defaults"
See references/phase-details.md for invocation summary.
See references/delegation-protocols.md for complete protocol.
Files generated:
- v[N]-ui.yaml (design specification)
- v[N]-ui-test.html (browser-testable mockup)
What would you like to do?
- Iterate - Refine design, adjust layout
- Finalize - Validate alignment and complete mockup
- Save as template - Add to aesthetic library for reuse
- Other
Choose (1-4): _
If user provides specific changes ("make it vertical", "add a meter", "change colors to blue"):
- Pass these as explicit requirements to new ui-design-agent instance
If user provides vague improvement requests ("make it better", "improve it", "polish it"):
- Prompt for specifics: "What aspect should I focus on? (layout, colors, spacing, controls)"
- If user says "everything" or "overall quality": Pass instruction to refine existing elements (spacing, color harmony, control styling) rather than add new elements
See references/decision-menus.md#phase-5-5-design-decision-menu for detailed routing.
See references/phase-b-enforcement.md for guard implementation.
See references/delegation-protocols.md for enforcement details.
After subagent returns stateUpdated: true, verify actual state contents match expected values (not just boolean flag).
Read .continue-here.md, parse YAML, check specific fields match JSON report values. If mismatch, present state recovery menu.
See references/state-tracking.md for complete state schema and verification protocol.
Purpose: Explore layouts without losing work, A/B test designs, keep history for rollback.
File naming: All 7 files prefixed with version (e.g., v2-ui.html, v2-PluginEditor.h).
Implementation: Latest version used for Stage 3 (GUI) unless user specifies different version.
See references/versioning.md for file management details.
- Phase 0:
references/aesthetic-integration.md - Aesthetic library integration
- Phase 1:
references/context-extraction.md - Creative brief extraction
- Phase 2-3:
references/design-questions.md - Question templates and tiering
- Phase 2.5:
references/layout-validation.md - Dimension calculation formulas
- Phase 4-5.45:
references/delegation-protocols.md - Subagent invocation
- Phase 5.5:
references/decision-menus.md - Menu format and routing
- Phase 5.6:
references/state-tracking.md - Brief sync protocol
- Phase 6-10:
references/phase-b-enforcement.md - Phase B guard
- Anti-patterns:
references/common-pitfalls.md - What to avoid
Technical details:
references/html-generation.md - Production HTML rules
references/browser-testing.md - Browser test workflow
references/cmake-configuration.md - WebView build settings
references/cpp-boilerplate-generation.md - C++ template generation
references/ui-design-rules.md - Design constraints and patterns
references/versioning.md - File management
1---2name: ui-mockup3description: Orchestrator for WebView UI mockup workflow - delegates design iteration to ui-design-agent and implementation scaffolding to ui-finalization-agent. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.4allowed-tools:5 - Read6 - Task7 - AskUserQuestion8preconditions:9 - None (can work standalone or with creative brief)10metadata:11 source: https://skillmd.com/skills/glittercowboy/ui-mockup12---1314<objective>15Creates WebView UI mockups for audio plugins through iterative design and implementation scaffolding.16</objective>1718<quick_start>191. Check for aesthetic library (Phase 0)202. Gather requirements through tiered questions (Phases 1-3)213. Dispatch ui-design-agent for mockup generation224. Iterate until user approves235. Generate implementation files24</quick_start>2526<workflow>27<phase name="A-design-iteration">28<purpose>Generate 2 design files for rapid iteration</purpose>29<outputs>30- `v[N]-ui.yaml` - Machine-readable design specification31- `v[N]-ui-test.html` - Browser-testable mockup32</outputs>33<gate>Do NOT proceed to Phase B until user approves design via Phase 5.5 decision menu</gate>34</phase>3536<phase name="B-implementation-scaffolding">37<purpose>Generate 5 implementation files ONLY after Phase A approval</purpose>38<outputs>39- `v[N]-ui.html` - Production HTML40- `v[N]-PluginEditor.h` - C++ header boilerplate41- `v[N]-PluginEditor.cpp` - C++ implementation boilerplate42- `v[N]-CMakeLists.txt` - WebView build configuration43- `v[N]-integration-checklist.md` - Implementation steps44</outputs>45<location>plugins/[PluginName]/.ideas/mockups/</location>46</phase>47</workflow>4849<context_detection>50<standalone_mode>51- No `.continue-here.md` file present52- Generates mockups independently53- Skips state updates54</standalone_mode>5556<workflow_mode>57- File `plugins/[PluginName]/.continue-here.md` exists with `current_stage` field58- Updates workflow state after each phase59</workflow_mode>6061Check for `.continue-here.md` existence to determine mode. If present, update state files. If absent, skip state updates.62</context_detection>6364<phase name="0-aesthetic-check">65Check if `.claude/aesthetics/manifest.json` exists. If found, count aesthetics using jq.6667<menu>68Found {N} saved aesthetics in library.6970How would you like to start the UI design?711. Start from aesthetic template - Apply saved visual system722. Start from scratch - Create custom design733. List all aesthetics - Browse library before deciding7475Choose (1-3): _76</menu>7778<routing>79- Option 1: Display aesthetics from manifest with metadata (name, vibe, colors, source). Invoke ui-template-library skill with "apply" operation. Skip to Phase 4 with generated mockup.80- Option 2: Continue to Phase 1 (load context).81- Option 3: Invoke ui-template-library skill with "list" operation, show previews, return to menu.82- No aesthetics: Skip directly to Phase 1.83</routing>8485See `references/aesthetic-integration.md` for complete integration details.86</phase>8788<phase name="1-load-context">89Load context from creative brief and extract requirements.90See `references/phase-details.md` for extraction protocol.91See `references/context-extraction.md#example-extracting-from-creative-brief` for examples.92</phase>9394<phase name="1.5-context-aware-prompt">95Adapt initial prompt based on creative brief contents (rich/minimal/zero UI details).96See `references/phase-details.md` for prompt templates.97</phase>9899<phase name="2-gap-analysis">100Analyze gaps in Tier 1 (Critical), Tier 2 (Visual), Tier 3 (Polish) requirements.101See `references/phase-details.md` for tier definitions.102See `references/design-questions.md` for question templates.103</phase>104105<phase name="2.5-calculate-dimensions">106Calculate recommended window size before asking user.107See `references/phase-details.md` for calculation steps.108See `references/layout-validation.md` Section 2 for formulas.109</phase>110111<phase name="3-question-batch">112Generate exactly 4 questions using AskUserQuestion based on identified gaps.113See `references/phase-details.md` for rules and question format.114See `references/design-questions.md#example-question-batches` for templates.115</phase>116117<phase name="3.5-decision-gate">118Present decision gate with AskUserQuestion: finalize, ask more questions, or add context.119Route to Phase 4, back to Phase 2, or collect free-form text.120See `references/phase-details.md` for menu format and routing.121</phase>122123<phase name="4-5.45-design-agent">124Invoke ui-design-agent via Task tool to generate YAML + test HTML.125126Include in invocation prompt:127- All gathered requirements (layout, controls, colors, etc.)128- Quality expectation: "Design must look like commercial $50-200 audio plugin - intentional decisions, not defaults"129130See `references/phase-details.md` for invocation summary.131See `references/delegation-protocols.md` for complete protocol.132</phase>133134<phase name="5.5-design-decision-menu">135<gate>CRITICAL: Phases 6-10 ONLY execute if user chooses option 2 (Finalize)</gate>136137<menu>138Mockup v[N] design created (2 files)139140Files generated:141- v[N]-ui.yaml (design specification)142- v[N]-ui-test.html (browser-testable mockup)143144What would you like to do?1451461. Iterate - Refine design, adjust layout1472. Finalize - Validate alignment and complete mockup1483. Save as template - Add to aesthetic library for reuse1494. Other150151Choose (1-4): _152</menu>153154<routing>155- Option 1 (Iterate): Collect refinement feedback, return to Phase 2 with new version (v2, v3, etc.), invoke NEW ui-design-agent instance (fresh context).156- Option 2 (Finalize): Proceed to Phase 5.6 (automatic brief update), mockup is source of truth for UI sections, no user interaction needed, continue to Phase 6-10 after brief sync.157- Option 3 (Save as template): Invoke ui-template-library skill with "save" operation, after saving return to Phase 5.5 menu.158- Option 4 (Other): Handle custom request (test in browser, validate constraints, etc.).159</routing>160161<iteration_guidance>162When collecting feedback for Option 1 (Iterate):163164**If user provides specific changes** ("make it vertical", "add a meter", "change colors to blue"):165- Pass these as explicit requirements to new ui-design-agent instance166167**If user provides vague improvement requests** ("make it better", "improve it", "polish it"):168- Prompt for specifics: "What aspect should I focus on? (layout, colors, spacing, controls)"169- If user says "everything" or "overall quality": Pass instruction to refine existing elements (spacing, color harmony, control styling) rather than add new elements170</iteration_guidance>171172See `references/decision-menus.md#phase-5-5-design-decision-menu` for detailed routing.173</phase>174175<phase name="5.6-update-brief">176Automatic update of creative brief from finalized mockup.177Triggered by "Finalize" selection in Phase 5.5.178No user interaction required.179See `references/phase-details.md` for protocol.180</phase>181182<phase name="6-10-implementation">183<prerequisites>184- User confirmed design in Phase 5.5 (selected option 2: Finalize)185- Phase A files exist (`v[N]-ui.yaml`, `v[N]-ui-test.html`)186- Finalization marker present in YAML187</prerequisites>188189See `references/phase-b-enforcement.md` for guard implementation.190</phase>191192<phase name="6-10.5-finalization-agent">193Invoke ui-finalization-agent via Task tool to generate 5 implementation files.194See `references/phase-details.md` for invocation summary.195See `references/delegation-protocols.md` for complete protocol.196</phase>197198<phase name="10.7-completion-menu">199Present completion menu after ui-finalization-agent returns successfully.200See `references/decision-menus.md#completion-menu` for format and routing.201</phase>202203<orchestration_protocol>204<delegation_rules>205This skill NEVER generates mockup files directly. ALL file generation delegated to subagents.206207<sequence>2081. Orchestrator: Gather requirements (Phases 0-3.5)2092. Orchestrator: Invoke ui-design-agent via Task tool2103. ui-design-agent: Generate YAML + test HTML, commit, return JSON2114. Orchestrator: Parse JSON, present Phase 5.5 menu2125. If iterate: Orchestrator invokes NEW ui-design-agent2136. If finalize: Orchestrator updates brief (Phase 5.6)2147. Orchestrator: Invoke ui-finalization-agent via Task tool2158. ui-finalization-agent: Generate 5 files, commit, return JSON2169. Orchestrator: Parse JSON, present completion menu217</sequence>218219See `references/delegation-protocols.md` for enforcement details.220</delegation_rules>221222<state_management>223Subagents update `.continue-here.md` with their phase results. Orchestrator verifies `stateUpdated` flag in JSON report.224225After subagent returns `stateUpdated: true`, verify actual state contents match expected values (not just boolean flag).226227Read `.continue-here.md`, parse YAML, check specific fields match JSON report values. If mismatch, present state recovery menu.228229See `references/state-tracking.md` for complete state schema and verification protocol.230</state_management>231232<iteration_protocol>233Each iteration runs in fresh agent context. User chooses "Iterate" then orchestrator collects feedback and invokes NEW ui-design-agent with incremented version. Fresh context prevents context window bloat during iterative design.234</iteration_protocol>235236<error_handling>237- Agent failures: Present error menu (retry/manual fix/debug/cancel).238- Validation failures: Agent returns `validationPassed: false` - present error menu.239- State update failures: Agent returns `stateUpdated: false` - present state recovery menu (verify/manual update/continue anyway).240</error_handling>241</orchestration_protocol>242243<versioning_strategy>244Pattern: v1, v2, v3... Each version saved separately.245246Purpose: Explore layouts without losing work, A/B test designs, keep history for rollback.247248File naming: All 7 files prefixed with version (e.g., `v2-ui.html`, `v2-PluginEditor.h`).249250Implementation: Latest version used for Stage 3 (GUI) unless user specifies different version.251252See `references/versioning.md` for file management details.253</versioning_strategy>254255<success_criteria>256<design_phase>257- YAML spec generated matching user requirements258- Browser test HTML works (interactive controls, parameter messages)259- Visual quality meets commercial standard (intentional design, not defaults)260- Design files committed to git261- `.continue-here.md` updated with version (if workflow mode)262- User presented with Phase 5.5 decision menu263- Design approved OR user iterates with refinements264</design_phase>265266<implementation_phase>267- All 7 files generated and saved to `.ideas/mockups/`268- Production HTML complete (no placeholders)269- C++ boilerplate matches YAML structure (correct parameter bindings)270- parameter-spec.md generated and locked (v1 only)271- Implementation files committed to git272- `.continue-here.md` updated with finalization status (if workflow mode)273</implementation_phase>274</success_criteria>275276<integration_points>277<invoked_by>278- `/dream` command - After creative brief, before implementation279- `plugin-workflow` skill - During Stage 0 (UI design phase)280- `plugin-improve` skill - When redesigning existing plugin UI281- Natural language: "Design UI for [PluginName]", "Create mockup for compressor"282</invoked_by>283284<always_invokes>285- `ui-design-agent` subagent (Phase 4-5.45) - REQUIRED for design iteration286- `ui-finalization-agent` subagent (Phase 6-10.5) - REQUIRED for implementation files287</always_invokes>288289<also_invokes>290- `ui-template-library` skill (if user saves aesthetic)291</also_invokes>292293<creates>294- `plugins/[Name]/.ideas/mockups/v[N]-*.{yaml,html,h,cpp,txt,md}` (7 files)295- `plugins/[Name]/.ideas/parameter-spec.md` (if v1 and doesn't exist)296</creates>297298<updates>299- `PLUGINS.md` - Mark UI designed (if workflow)300- `.continue-here.md` - Update workflow state (if workflow)301</updates>302303<blocks>304- Stage 1 (Foundation) - Cannot proceed without parameter-spec.md305- Stage 3 (GUI) - Cannot implement without approved UI mockup306</blocks>307</integration_points>308309<reference_documentation>310Progressive disclosure - load references when reaching specific phases:311312- **Phase 0:** `references/aesthetic-integration.md` - Aesthetic library integration313- **Phase 1:** `references/context-extraction.md` - Creative brief extraction314- **Phase 2-3:** `references/design-questions.md` - Question templates and tiering315- **Phase 2.5:** `references/layout-validation.md` - Dimension calculation formulas316- **Phase 4-5.45:** `references/delegation-protocols.md` - Subagent invocation317- **Phase 5.5:** `references/decision-menus.md` - Menu format and routing318- **Phase 5.6:** `references/state-tracking.md` - Brief sync protocol319- **Phase 6-10:** `references/phase-b-enforcement.md` - Phase B guard320- **Anti-patterns:** `references/common-pitfalls.md` - What to avoid321322Technical details:323- `references/html-generation.md` - Production HTML rules324- `references/browser-testing.md` - Browser test workflow325- `references/cmake-configuration.md` - WebView build settings326- `references/cpp-boilerplate-generation.md` - C++ template generation327- `references/ui-design-rules.md` - Design constraints and patterns328- `references/versioning.md` - File management329</reference_documentation>330331<template_assets>332- `assets/ui-yaml-template.yaml` - YAML structure333- `assets/webview-boilerplate.md` - C++ integration templates334- `assets/integration-checklist-template.md` - Integration guide335- `assets/parameter-spec-template.md` - Parameter specification format336</template_assets>