ui-mockup
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]'.
When & Why to Use This Skill
The ui-mockup skill is a professional-grade orchestrator designed to automate the WebView UI design and implementation workflow for audio plugins. It streamlines the transition from conceptual design to production-ready code by coordinating specialized agents for iterative mockup generation and technical scaffolding. By managing complex multi-phase tasks—including aesthetic selection, requirement analysis, and the generation of C++, HTML, and CMake files—it ensures high-fidelity user interfaces that meet commercial standards while significantly reducing manual development overhead.
Use Cases
- Rapid Audio Plugin Prototyping: Generate interactive, browser-testable WebView mockups for audio plugins (VST/AU) based on specific aesthetic templates or custom briefs.
- Automated UI Scaffolding: Produce complete implementation packages including C++ headers (.h), implementation files (.cpp), and CMake configurations for seamless integration into plugin projects.
- Iterative Design Refinement: Manage a multi-agent feedback loop where users can refine UI layouts, controls, and visual styles through version-controlled iterations before finalizing code.
- Cross-Platform UI Standardization: Ensure consistent UI specifications and parameter bindings across different development environments using machine-readable YAML design specs.
| name | ui-mockup |
|---|---|
| description | 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]'. |
Check for .continue-here.md existence to determine mode. If present, update state files. If absent, skip state updates.
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.
- 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): _
- Option 1 (Iterate): Collect refinement feedback, return to Phase 2 with new version (v2, v3, etc.), invoke NEW ui-design-agent instance (fresh context). - 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. - Option 3 (Save as template): Invoke ui-template-library skill with "save" operation, after saving return to Phase 5.5 menu. - Option 4 (Other): Handle custom request (test in browser, validate constraints, etc.). When collecting feedback for Option 1 (Iterate):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 rulesreferences/browser-testing.md- Browser test workflowreferences/cmake-configuration.md- WebView build settingsreferences/cpp-boilerplate-generation.md- C++ template generationreferences/ui-design-rules.md- Design constraints and patternsreferences/versioning.md- File management