Design System API Alignment

A component API defined once by design and once by engineering, each working independently, produces two APIs that don't match — different prop names, different anatomy, different assumptions about what's optional. Alignment between the two isn't a byproduct of everyone having good intentions; it's a deliberate, staged process with its own owners, artifacts, and done criteria. This skill runs that process. It is deliberately silent on what the API itself should look like — naming conventions, anatomy rules, and prop-design judgment are eg-component-api-design's job; this skill governs how design and engineering converge on whatever API that discipline shapes.

Principles