Overview
A component with a bad API is worse than no component. It gets used incorrectly, generates support tickets, accumulates workarounds, and eventually gets forked by every team that hits its limits. The API is not an implementation detail — it is the contract between the design system and every team that depends on it. Breaking that contract has a cost that compounds with every new consumer.
The Component API Design Prompt builds the API conventions that make a component library consistent from the outside — so engineers can predict how any component works based on how any other component works, and designers can map their decisions directly to props without a translation layer.
What you get: - Prop naming convention: the complete naming standard for variants, states, sizes, and behaviors - Variant model: when to use a variant prop vs. a compound component vs. a separate component - Composition model: the slot pattern and render prop patterns that make components extensible without modification - State management contract: how components communicate state to consumers and accept state from them - TypeScript interface standard: the type structure that makes prop tables self-documenting - Escape hatch design: the `className`, `style`, and `as` prop patterns that allow customization without forking
Built for: design engineers and front-end architects designing the API layer of a component library in React, Vue, or Angular.