composable-components
Installation
SKILL.md
Composable Components
Design the public composition contract before arranging files. A namespace and
Root / Trigger / Content names do not make an API composable: consumers
must be able to use the advertised parts without the implementation silently
replacing, ignoring, or trapping them behind fixed defaults.
This skill is self-contained. Do not require another skill to make the API, state, rendering, accessibility, or layout decisions described here.
1. Classify behavior and rendering ownership
| Kind | Signals | Public shape | Contract |
|---|---|---|---|
| Primitive | reusable behavior, asChild, dialog/select/accordion anatomy |
Root plus semantic parts such as Trigger, Content, Portal, Overlay, Title, Description, Close |
Primitive contract |
| Product | domain data, feature variants, mode-prop growth, local or synced state | Provider + Frame when the state scope differs from the visual frame; otherwise Root plus domain parts |
Product contract |
Installing or merely assembling already-authored component packages is outside scope. This skill is for authoring or refactoring component APIs.