UI Router

Use this skill when a product UI request is ambiguous or spans several stages. Select a clear leaf task directly. Bible owns the route and personal constraints; original author skills stay under their native plugin or reviewed upstream ownership. Read complete provider instructions and prerequisites from the current-session catalog. Missing providers or connections are unresolved dependencies, not a reason to recreate an author workflow locally. Files on disk do not establish host exposure or a working connection.

Choose one primary skill and at most one supporting skill by default. State the route only when a handoff or provider limitation matters. Reuse the established route and already-read instructions for same-task follow-up turns.

Routing

• Working screens for dashboards, CRM, ERP, admin or internal business tools with several UI concerns -> ui-business-apps.
• Clear dense-interface design -> interface.interface-design; specific pattern/stack research -> uipro.ui-ux-pro-max; targeted UX critique or refinement -> impeccable.impeccable. Select these leaves directly.
• New visual direction or major redesign without a sufficient current design reference -> ui-concept-first.
• Evidence, critique, compare, improve, or "what do other apps do" -> ui-research.
• Extract tokens, typography, components, or responsive rules from a reference -> design-system-extractor.
• Figma selection/frame/component to frontend code -> figma-to-code.
• Existing code/live UI back to Figma or Code Connect -> code-to-figma.
• Landing pages, portfolios, editorial sites, redesigns, image-led website concepts, mobile app concepts, image-to-code work, general frontend UI, or style-constrained builds -> ui-build.
• Figma work -> ui-figma.
• Rendered frontend QA, visual diff, browser testing, perf review, or code review -> ui-qa.

Rule

Read each selected provider's complete SKILL.md before its use. A matching existing design system is a sufficient visual reference; ordinary component changes do not require generated concepts or repeated approval. Provider setup, authentication and publishing are separate from selecting a route.