Design shared components that hundreds of engineers can use correctly: naming, variants vs. booleans, polymorphism, escape hatches, accessibility by default, and evolving APIs without breaking consumers.
When a component is used in 3 places, its props are an implementation detail. When it's used in 3,000 places across 40 teams, its props are a public API, with the same properties as any other API:
Good design-system APIs share some traits:
<Button>Save</Button> should just work: correct semantics, focus ring, and the default variant.primary and danger, don't offer two booleans.type, disabled, aria-*, onClick) instead of inventing your own (isDisabled, handleClick).className, style, and ref forwarding, so teams aren't forced to fork.size is always "sm" | "md" | "lg", never small in one place and compact in another.