feat: add ui_design_specialist (Phase 3 UI Design) v0.2.0

- New specialist: ui_design_specialist with iterative mockup dialog
- New Phase 3 (UI Design) between Architecture and Implementation
- Relay model: orchestrator passes responses verbatim in Phase 3
- Cost-control exception for UI Design phase (unlimited subagent calls)
- Webspace mockup workflow with cache-buster and obscure dirs
- UX states coverage (loading, empty, error, partial)
- WCAG 2.1 AA accessibility guidelines
- Design tokens (CSS custom properties) in design system
- Component states (hover, focus, active, disabled, loading, error)
- Sitemap/wireframe before mockups for complex UIs
- Real content strategy (no Lorem Ipsum)
- Form validation UX in mockups
- Dark mode and i18n support (optional)
- Design handoff support (specialist available during implementation)
- Skip mechanism for non-UI projects
- Mockup state file for context compression recovery
- Multi-page mockup strategy with index.html
- task_graph.json mockup references
- Plugin version: 0.1.14 -> 0.2.0
- 47 files changed across 7 implementation blocks
- 3 review rounds with 41 corrections integrated
This commit is contained in:
Software Orchestrator
2026-06-19 21:33:21 +02:00
parent 2343f0e717
commit f6691b74f6
44 changed files with 995 additions and 40 deletions
@@ -18,7 +18,7 @@ You are the implementation_engineer subagent. The orchestrator delegates to you
0. Verify plan_mode allows implementation (.a0/orchestrator_mode.json).
1. Read the selected task from .a0/task_graph.json.
2. Update task status to in_progress.
3. Read context files needed for the task (related specs, existing code).
3. Read context files needed for the task (related specs, existing code). If UI Design phase (Phase 3) produced artifacts, read ui_design.md, mockup URLs, component_inventory.md, design tokens, and UX states documentation. Mockups are visual targets — use them as design reference during implementation. For design questions, ask orchestrator to call ui_design_specialist (Design Handoff Support).
4. Implement the change as a focused diff.
5. Run available tests/builds for the affected component.
6. Update task status to completed or blocked.