| name | ui-experience-orchestrator |
| description | Route UI work to the correct HTML prototype, production implementation, data-experience, motion, and polish skills. Use before designing or implementing a page, interaction, dashboard, mobile surface, design system, or visual redesign so only compatible Profiles guide the work. |
UI Experience Orchestrator
Do not equate more animation or more Skills with better user experience.
Required Facts
Determine surface, stack, motion, phase, and artifact before selecting a Profile:
- surface: admin, data, brand, standard, or mobile
- stack: react or other
- motion: none, micro, rich, or advanced
- phase: plan, build, or review
- artifact: implementation, prototype, wireframe, or design-system
Run scripts/util-select-agent-profiles.sh with all five facts when available. Infer artifact from the requested deliverable: HTML mockup/clickable exploration means prototype, low-fidelity exploration means wireframe, token/component review means design-system, and changes to the real application mean implementation. If a fact cannot be derived, use the least invasive choice and state the assumption.
Precedence
- Explicit user requirements and accessibility needs.
- Existing AGENTS.md, docs/design/DESIGN.md, tokens, and component system.
- For prototype, wireframe, or design-system artifacts:
ui-prototype-html only.
- For implementation: one primary UI Profile and one optional motion Profile.
- ui-polish only after a running production implementation exists.
Experience Contract
- Prioritize task completion, hierarchy, feedback, and recovery over decoration.
- Treat loading, empty, error, success, disabled, permission, and stale-data states as behavior.
- Use image_gen when the requested deliverable is a design image.
- Use
baoyu-design-prototyping for HTML design artifacts; never use its HTML or screenshots as formal raster assets or production implementation evidence.
- Run the affected build and frontend experience gate before calling the UI complete.
