Ui Build

---
name: ui-build
description: "Routes UI implementation to original skills for websites, dashboards, CRM, and administrative applications."
---

# UI Build Router

Use this skill to select a design or implementation provider. For a clear task,
select the leaf directly; an established route remains valid on follow-up turns.

Read the complete original `SKILL.md` and required references from the
current-session catalog. Keep reviewed upstream and native plugin ownership;
installed files alone do not prove exposure. A missing provider needs its
official setup or reviewed dependency, never a local workflow replacement.

## Routing

- Working screens for dashboards, CRM, ERP, admin tools or other business apps
  -> `ui-business-apps`; its owner policy chooses the author design provider.
- Clear dense-interface design or system-consistency task ->
  `interface.interface-design`.
- Pattern, chart, typography or stack guidance for a specific UI ->
  `uipro.ui-ux-pro-max`.
- UX shape, targeted refinement or hardening -> `impeccable.impeccable`, using
  the author's command/reference for that request and Operate mode for app UI.
- Major new visual direction with no sufficient reference -> `ui-concept-first`.
- Extracting implementation constraints from a visual reference ->
  `design-system-extractor`
- Figma frame/selection/component implementation -> `figma-to-code`
- Frontend pages, components, app or dashboard implementation ->
  `build-web-apps:frontend-app-builder`
- Analytics, data storytelling, chart choice or visualization implementation
  -> `build-web-data-visualization:data-visualization`
- Image-based alternatives or mobile concepts -> `product-design:ideate`
- Translate a selected visual into code -> `product-design:image-to-code`
- Implement from a live URL reference -> `product-design:url-to-code`
- Build a complete Sites website -> `sites:sites-building`
- shadcn/component composition -> `build-web-apps:shadcn`
- React/Next.js implementation performance -> `build-web-apps:react-best-practices`
- Strong style constraints -> an exposed author design skill matching the brief;
  preserve the original provider and the user's selected visual direction.

## Rule

Use an existing design system or verified current screen as the visual target
when it fits the task. Do not force image generation or a fresh concept approval
for ordinary changes. Select `ui-qa` only for the evidence the implementation
needs; use `playwright-visual-qa` when visual fidelity is material.