UI Router

Route UI work to the smallest effective set of specialized UI skills. The goal is to use the right skills in the right order, not to produce a routing report.

Read references/ui-skill-catalog.md when the request needs skill selection. The catalog lists public UI skills, their purposes, and source repositories.

Route the Work

1. Identify the product context and current phase:
   • new UI: establish direction, then implement;
   • existing UI: critique before changing broad visual behavior;
   • defined problem: route directly to the narrow repair skill;
   • completed implementation: audit, then polish.
2. Choose one primary skill that owns the main decision or implementation.
3. Add supporting skills only when they have separate jobs. Two or three skills are normally enough.
4. Keep one visual direction. Do not combine Apple, minimalist, brutalist, high-end, and other competing taste skills unless the user asks to compare directions.
5. If the user asks for implementation, invoke the primary skill and proceed. Apply supporting skills in sequence when their phase arrives.
6. If the user only asks which skill to use, answer with the primary skill, optional supporting skills, and one short reason.