Baseline UI
A compact, opinionated baseline for spacing, typography, and interaction code.
The field guide
One moment.
Loading the selection…
The field guide
Loading the selection…
A closer look / 9 skills
Find AI skills for shadcn/ui components, React composition, and interface cleanup. Choose guidance that fits your project and component task.
A compact, opinionated baseline for spacing, typography, and interaction code.
Reshape growing React component APIs with composition and explicit state boundaries.
Product-interface polish with attention to motion and component behavior.
Native screen styling, semantic colors, controls, and visual effects for Expo.
Implement Figma designs using design context, real assets, and existing components.
Product-interface direction with design decisions saved across sessions.
Prioritized React and Next.js guidance for data flow, bundles, and rendering.
Guide route, state, and shared-element transitions with React’s transition APIs.
Project-aware guidance for installing, composing, and customizing shadcn/ui.
Choosing a skill
Component work ranges from assembling a familiar control to untangling an API that has grown difficult to change. Name the component, its states, and its existing dependencies before selecting a skill. This makes it easier to preserve working behavior while improving how the interface is built.
Use guidance that checks project configuration and existing components before making changes. It covers component discovery, composition, and customization, with attention to the primitive library and styling conventions used by the project.
Read the shadcn/ui reviewChoose composition guidance when boolean props and shared state make a reusable component difficult to understand. It covers compound components and state boundaries; check the React version before applying its version-specific recommendations.
Read the Composition Patterns reviewApply a focused baseline for spacing, typography, controls, and interaction states in a Tailwind project. Its defaults are deliberately restrictive, so provide any approved visual or motion rules that should take precedence.
Read the Baseline UI reviewGive the agent examples of current usage and the states the component must support. After the change, test its consumers, keyboard behavior, and narrow layouts. Use a separate visual brief when the unresolved question is the overall direction of the page.