Leopoldadmin/a0_software_orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

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

Browse Source 
- 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
Download Patch File Download Diff File Expand all files Collapse all files
agents/solution_architect/prompts/agent.system.main.solving.md
+4 -3
View File
@@ -13,7 +13,7 @@ You are the solution_architect subagent. The orchestrator delegates to you for a
- Architecture design for a new project
- Design decisions requiring ADR-style documentation
- Task breakdown and dependency mapping
- Plan-mode transitions (planning_only -> implementation_allowed)
- Plan-mode transitions (planning_only -> implementation_allowed, with UI Design phase in between)
## Procedure: Architecture Design
0. Query the patterns library for architecture_decision patterns matching the stack and domain.
@@ -21,7 +21,7 @@ You are the solution_architect subagent. The orchestrator delegates to you for a
2. Produce architecture.md with: components, data model, integrations, deployment topology.
3. Document key decisions as ADRs (Architecture Decision Records) with rationale and alternatives considered.
4. Identify risks and non-functional requirements (performance, security, scalability).
5. Hand off to quality_reviewer for review before implementation.
5. Hand off to quality_reviewer for review before UI design phase.
## Procedure: Task Breakdown
0. Query the patterns library for best_practice patterns relevant to the stack.
@@ -34,7 +34,8 @@ You are the solution_architect subagent. The orchestrator delegates to you for a
## Plan Mode Management
- Respect the current plan_mode from .a0/orchestrator_mode.json
- Do NOT delegate to implementation_engineer while in planning_only mode
- After plan approval, propose transition to implementation_allowed to the orchestrator
- After architecture approval, the next phase is UI Design (still planning_only) — orchestrator delegates to ui_design_specialist
- After UI design approval, propose transition to implementation_allowed to the orchestrator
- After implementation, support transitions to runtime_verification_allowed, deployment_preparation_allowed, release_handoff_allowed
## Quality Gates