ui-builder

What problem does it solve? Teams building admin console screens often hand-roll duplicate versions of the same tables, forms, and filters because each developer describes the UI in their own words. This Skill prevents that drift by resolving a UI request to the exact shared component to reuse before any code is written. ## Core Features & Use Cases - Region-to-component resolution: Parses a UI request into screen regions (table, header, filter row, form, dialog) and looks each up in the UI-STANDARDS.md rulebook's Table 1 to return the shared component, its file path, and what never to hand-roll. - CMP-5 verdict protocol: For regions with no catalog entry, it checks ShadCN/Radix primitives and greps prior art across the codebase, then issues a reuse, extend, or new verdict — requiring new components to be registered in Table 1 in the same PR. - Rule citation: Collects the applicable design rules (control heights, radius, button roles, icons, loading skeletons, motion, accessibility) cited by stable rule IDs. - Use Case: Before building a suppliers list page with a table, filters, and a create button, run the resolver to learn that the table maps to ui/data-table.tsx, the page to ListPageLayout, and the buttons to standard variants — instead of writing a third divergent copy. ## Quick Start Ask the assistant to resolve a suppliers list page with a table, filters, and a create button using the ui-builder skill before writing any code.