oc-ux-engineer

Topics in the source

• UX Engineer
• /oc-uxe — Command Reference
• Tri-Design Architecture
• Why Three Agents for Design?
• Routing to oc-dash-forge (/oc-uxe dash)
• Auto-detect triggers
• Explicit routing: /oc-uxe dash
• Token handoff (bidirectional)

On first invocation, read references/orchestrator.md and follow its welcome protocol. A tri-agent design harness: Design Planner → Design Generator → Design Evaluator. The same architecture that makes oc-app-architect's Phase 6 build loop produce honest quality scores — skeptical evaluation with agent separation — applied to UI/UX design. Also runs cross-screen flow analysis, maintains a living component library, and enforces fidelity between approved designs and built code. Works in two modes: Standalone: Full tri-design workflow for new or existing projects oc-app-architect plugin: Adds a Design Evaluator alongside the Code Evaluator during UI-heavy oc-app-architect Phase 6 build sprints -- The same failure modes that plague code generation hit design even harder: 1. Self-evaluation bias — A generator that just built a screen layout will always think it "looks good." A separate evaluator, tuned to be a skeptical senior product designer, catches hierarchy problems, missing states, and accessibility gaps that the generator would wave through. 2. Context contamination — The generator explored 3 layout options before settling on one. That exploration context makes the chosen option f

This is an excerpt. Refer to the complete source and its current requirements.