Miltinson Design System
Practical components, honestly built.
I run several small products under one name, and this system keeps them consistent and fast to ship — tokens, React components, and AI patterns that work the same way in every app. No fluff, no dark patterns, accessible by default.
- components
- 44
- interaction hooks
- 6
- design tokens
- 151
- published packages
- 3
What the system believes
Ink-led, one loud color
Black type, white surfaces, hairline borders. Miltinson Amber is the only shout — a signal, never a fill.
Sharp, not pillowy
4–6px radii, borders doing the work shadows usually do, and motion that confirms instead of performing.
Accessible by default
WCAG AA pairings, 16px minimum text, visible focus rings, scoped touch targets, reduced motion honored — built into the tokens, not bolted on.
Agents are users too
A generated manifest feeds the props tables, the search index, and machine-readable endpoints — so an AI writing against this system imports the right thing on the first try.
Find your way in
Foundations
Color, type, spacing, radii, motion — rendered live from the tokens package.
Components
All 44 components with live demos, generated props tables, and keyboard contracts.
Patterns
Header, hero, forms, data display — recipes composed from primitives.
Guidelines
Voice, the accessibility standard, tier boundaries, and how to contribute.
Build with AI
llms.txt, per-component JSON, and prompt templates that ship with the packages.
Installation
GitHub Packages auth, two imports, and the starter generator.
Pointing an agent at this?
Fetch /llms.txt for the index, /llms-full.txt for the whole corpus, or /r/<component>.json for one component's machine-readable record. Import paths in those files are real — they resolve against the published packages.