UI Mockup

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?

1. Start from aesthetic template - Apply saved visual system
2. Start from scratch - Create custom design
3. 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?

1. Iterate - Refine design, adjust layout
2. Finalize - Validate alignment and complete mockup
3. Save as template - Add to aesthetic library for reuse
4. 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