designsystemetlisted
Install: claude install-skill sorensensig/ai-corner-store
# Designsystemet
Designsystemet's prop surface is not what a general React prior predicts, and its
accessibility requirements are mostly *consumer* responsibilities the components do not
enforce for you. Both are served by the `designsystemet-twins` MCP. Look them up; do not
recall them.
## First move — before writing any code
| You are about to… | Call | Then |
|---|---|---|
| Build a screen, form, or flow | `get_pattern("<slug>")` | The pattern names the components, their order, the timing rules, and the a11y wiring. Components alone will not give you a correct form. |
| Use a named component | `get_component("<slug>")` | The real export name, the a11y rules the component does not enforce, the token mapping, and the docs links carrying the full prop tables. |
| Port markup from another design system, or resolve a `data-registry` / `ds-*` value off a rendered page | `find_equivalent("<term>")` | Then `get_component` on the match. |
| Not know what exists | `list_twins()` | Inventory with one-line summaries. |
If a component has no twin, the pattern twin still names its role and its rules — read that
rather than guessing a prop surface. A missing twin is a reason to look wider, never a
licence to invent.
## Level 1 — which component for which intent
Cross-component knowledge, true before anything is chosen. Level 2 (the contract for
whatever you choose) lives in the twins.
| Intent | Component | Not the neighbour, because |
|---|---|---|
| Tell the user something about