Build a Component Library
Give components one API, one place to try them, and an honest way to retire them.
The steps
Your agent works through these in order, and won't break a step it already finished.
Component Variant API
Give every component one consistent way to express size, tone, emphasis, and state.
Compound Component Pattern
Let related parts of a component share state while the caller keeps control of the arrangement.
Slot-Based Composition
Let components take content in named positions instead of accumulating a prop per element.
Polymorphic Components
Reuse one visual component while it still renders the element the browser needs.
Component Prop Guardrails
Make impossible prop combinations fail at the point of use rather than in production.
Component Playground
Render every component in isolation, in every state, with its props adjustable.
Component Usage Documentation
Put the rules for using a component next to the component, where they get read.
Component Changelog
Record what changed in the shared components so consumers are not surprised by a release.
Component Deprecation Path
Retire old components and props gradually instead of breaking every screen at once.
How to use this collection
One link, several features, one coherent document. Your agent inspects your app once — not once per feature — then implements the set in order, checking after each step that it hasn't broken the last.
Pro users build their own from any features in the library, including their own customized versions.
Go Pro — $28/month