What problem does it solve? Building a frontend that feels like a real product rather than a generic template requires coordinating design direction, component libraries, motion, accessibility, and state coverage, which is easy to get wrong when done ad hoc. ## Core Features & Use Cases - Phased UI orchestration: Runs a structured pipeline from clarification brief through design tokens, component architecture, motion design, and a final verification gate. - Library routing: Maps each interaction need (dialogs, toasts, forms, tables, command palettes, drawers, virtual lists) to the right library skill such as base-ui, Sonner, react-hook-form, TanStack Table, cmdk, and Vaul. - Quality enforcement: Applies anti-slop rules, a finish-gate checklist covering all component states, dark mode, reduced motion, responsive behavior, and accessibility. - Use Case: When asked to build a dashboard, it clarifies the vibe and animation dial, picks tokens, composes components from primitives, adds purposeful motion, and audits the result before shipping. ## Quick Start Ask the agent to build the frontend for your app and answer the short UI engineering brief about audience, vibe, and animation level.
