These are the 22 colours the Corridor app actually uses. Components never reference them directly. The role under each swatch is a hint; the real job is set in layer 2.
Change a brand colour once and every button, badge and chart follows. Components only ever read semantic tokens, which is also what makes a dark theme or a second brand possible without touching components.
Naming rule: category.role.variant.state. The same names are used for Figma variables, CSS custom properties and the JSON file, so design and code never need a translation table.
✓ Do
Pair every status colour with a word or icon. "Failed" is red and says Failed.
✕ Don't
Use Saffron for text on light backgrounds (1.6:1). It is for highlights, the accent button and focus on teal.
✓ Do
Reach for a semantic token first. If none fits, propose one (see Governance) instead of using a primitive.
Only 700 and 800 are used, which keeps money and labels confident on small screens. Amounts always use tabular figures so columns of numbers line up. Nothing on screen goes below 12px (one known gap is listed under Accessibility).
Half steps (6, 10, 14) are allowed inside compact parts like chips and badges.
sm icon tiles · md inputs · lg list panels · xl cards · pill buttons and chips.
Surfaces are separated by colour first. Shadows are kept for things that float.
Each component is specified for default, hover, focus-visible, pressed, disabled and loading. Tags show what is already built into the Corridor prototype and what is specified for the build.
Three variants, live. Hover, tab to focus, or press and hold.
| Prop | Values | Default | Rule |
|---|---|---|---|
| variant | primary | tonal | accent | primary | One primary per screen |
| size | md 44px | lg 54px | lg | Never below 44px tall |
| icon | leading icon, optional | none | Icon is aria-hidden; the label carries meaning |
| loading | boolean | false | Keeps width, shows spinner, sets aria-busy |
| disabled | boolean | false | Label must say why ("Not enough balance") |
| fullWidth | boolean | true | Bottom action bars |
Filled, no stroke. The helper line is always reserved so the layout never jumps. Errors are announced with aria-describedby and aria-invalid.
Fee shown before you confirm.
Chips: selected uses color.action.primary, unselected color.bg.fill. Switch: 52 × 32 with a 44px hit area, role="switch".
12 · 700, padding 4 × 8, pill. Always a word plus an icon, never colour alone.
Ratios are calculated with the WCAG 2.x formula from the exact hex values above. The target is WCAG 2.2 AA. Where the prototype misses a rule, it is listed rather than hidden.
| Pair | Ratio | WCAG | Where |
|---|---|---|---|
| Ink on Paper | 17.0:1 | AAA | Body text, amounts |
| White on Teal 900 | 11.9:1 | AAA | Primary button, balance card |
| Teal 900 on Saffron | 6.8:1 | AA | Accent button |
| Slate 500 on White | 5.9:1 | AA | Captions on cards |
| Slate 500 on Sand 200 | 4.8:1 | AA | Input hints |
| Teal 200 on Teal 900 | 9.1:1 | AAA | Secondary text on teal |
| Green 700 on Green 100 | 5.5:1 | AA | Arrived badge |
| Amber 700 on Saffron 100 | 4.9:1 | AA | In progress badge |
| Red 600 on White | 5.4:1 | AA | Error messages |
| Red 600 on Red 100 | 4.4:1 | Fails | Failed badge, fix in v1.3 |
| Saffron on Paper | 1.6:1 | Never text | Decoration only |
| Focus ring Teal 900 on Paper | 10.8:1 | Passes 3:1 | Non-text: focus indicator |
Found by auditing the build against these rules. Scheduled for v1.3.
Durations are grouped by what moves. Small things move fast; things that change the screen take longer; celebration is rare.
Press (scale .96, 150ms), colour changes (200ms), switch knob (250ms).
Sheets (400ms), drawers (350ms), screen enter (450ms, fade and rise).
Chart bars grow (700ms). Confetti (2.4s) only when a transfer succeeds.
One easing curve for the whole app: motion.ease.out = cubic-bezier(.2,.7,.2,1). Under prefers-reduced-motion every keyframe animation is removed. The portfolio site around this page has its own motion layer; it is not part of Corridor.
A system is only as good as the way it changes. This is the contribution and release process I use, shown here on Corridor.
A short request: the problem, screenshots of where it appears, and why an existing component does not fit.
Design and engineering review together, weekly. Checked against contrast, 44px targets and the full state list.
Figma component on variables and code component on the same token names. Every state from the matrix, both sides.
Version bump, changelog entry, short note to the team. Deprecated tokens stay one minor version with a warning.
v1.0 and v1.1 are sample entries for this concept.