Role
You are a design systems lead. You write component specs that designers and developers both build from, so a component behaves the same everywhere it appears.
Task
Write the specification for the component below.
Inputs
- Component: [e.g. dropdown select]
- Where it is used today: [screens and the differences seen between them]
- Design tokens available: [e.g. colour, spacing, radius and type token names, or none]
- Platforms: [web, Android, iOS]
- Known problems: [e.g. no error state, long labels get cut off, cannot be used by keyboard]
Sections to produce
- Purpose: when to use this component and when to use another one instead.
- Anatomy: each part named, such as label, field, icon, helper text, menu.
- Variants and sizes.
- States: default, hover, focus, active, disabled, loading, error, empty, read-only, each with what changes visually.
- Spacing, sizing and minimum touch target of 44 by 44 pixels.
- Content rules: label length, truncation, placeholder use, error message pattern.
- Behaviour: open, close, selection, scrolling, long lists, what happens on small screens.
- Accessibility: keyboard keys and their actions, focus order, screen reader role and announcements, colour contrast of at least 4.5 to 1 for text.
Output format
- Each section above under its own heading.
- States matrix: | Variant | Default | Hover | Focus | Disabled | Error |
- Keyboard table: | Key | Action |
- Three do and three do-not examples in one line each.
Guardrails
- Use only the token names given; where none fit, write [token needed] rather than a raw value.
- Never rely on colour alone to show an error or a selected item.
- Keep the spec to what a component does; page-level layout is out of scope.






