Wiki · Design kit
One design system. Everything else builds on it.
Websites, SaaS dashboards, reports, emails and decks all draw from the same set of tokens and templates, so a client recognises the work as ours whichever of those it arrives as — and so changing a colour or a spacing rule means changing it once.
TokensOne set of values — colour, spacing, type — that every website, report, email and deck reads from. Change a value here and it changes everywhere it is used, instead of thirteen files each holding their own guess at the same brand colour.
The pinEvery consumer points at a specific, named version of the kit rather than copying its files into their own repo. A copy drifts silently; a pin either matches or it doesn’t, and everyone can see which.
The drift gateAn automated check that fails a build the moment a page stops matching the pinned tokens — the thing that catches a stale copy before it ships, rather than a person noticing months later.
Anti-slop rulesExplicit, written bans on the choices that make AI-generated output look generic — the default gradients, the default rounded-card-with-shadow layout, the default font pairing. Followed on purpose, not by accident.
A real one
The layout-QA report, built from the same tokens as every other page on this site —open the full report ↗
Where it shows up
WebsiteLanding pages and marketing sites — one hero layout, one accent colour, the same type pairing every time.
SaaSProduct dashboards — KPI strips, charts and tables that look like they belong to the same product as the marketing site.
Reports & emailEvery check any of the 97 skills runs writes to this. See the report kit for the verdict legend and a real example.
DecksSlide layouts for client-facing presentations, built on the same tokens rather than a generic template picked fresh each time.
Not pinned in this build — set DESIGN_KIT_ROOT to render live token data. For the token source files, template paths and the drift-check script —Toolkit-os/design-kit, starting at design-kit/docs/REPO_SHAPE.md.