Token documentation & component library

One governed token graph, not a components folder every team forks and drifts from.

Most design systems ship a components folder — files, a Storybook, a package to install. The moment a team needs something the library doesn't have, they fork it, and the fork drifts from the source. This system ships the token graph itself: DTCG-native, self-hostable, and readable directly by the codegen agents that consume it, not just by designers.

Every token, every component recipe, and every research decision behind it lives in one versioned source — browse it below, or download the whole graph as a bundle.

108components & elements
389tokens
DTCG-nativeApache-2.0 tokens & bundles
Also built on these tokens
One source of truth

Everything on this site is read from one registry.

Navigation, the counts on this page, the machine API, and every download all resolve against the same registry file. A component that isn't registered can't appear in the nav, and a count here can't drift from what a release actually contains — there is exactly one place any of these numbers come from.

dtcg-vault/ — single source of truth
NavTokens / Components / Product lines (Knowledge Platform, GIS, Org Charts) / Writing / Paper / Self-host / Agents / Releases
Homepage statsCounts rendered above, same numbers the registry serves
Machine APIMCP tools + component/token endpoints — what agents query
DownloadsBundle downloads — nothing served that isn't registered

A published count, a navigation entry, and a bundle download all resolve against the same registered record.

Four token domains, one Apache-2.0 graph.

Every domain below is DTCG JSON under Apache-2.0 — pull the whole graph or just the pieces you need into your own build, with no server required.

Tokens

The full token set

  • Color, type, spacing
  • Motion, elevation, status
  • Accessibility targets
Components

Recipes, not screenshots

  • HTML + CSS + ARIA per component
  • Carbon-baseline reference where one exists
  • Machine-readable via the registry
Writing

Voice, versioned like tokens

  • Voice, registers, mechanics
  • Terminology A–Z
  • Worked before/after pairs
Paper

Document-format tokens

  • Page geometry, pagination counters
  • Four-step rule-weight ladder
  • Built for subscription agreements, disclosure documents, and other regulated print formats
Optional

Or run the whole publishing stack yourself.

The tokens above are complete on their own — nothing on this page requires a server. The same engine that runs this site, app-privategit-design, is also available for a different company to publish and govern its own design system on: its own tokens, its own change history, its own on-prem MCP endpoint, inside its own infrastructure. That's a separate product from what's on this page.

Every number below is live.

There's no separate cached copy of this data — the server reads the same dtcg-vault/ directory the numbers below are counted from, every time.

108
Components
389
Tokens
4
MCP tools
6
Paper document families
$ curl https://design.pointsav.com/components/button/recipe.json # Example response {   "name": "button",   "category": "components",   "registry_type": "component",   "variants": [{ "name": "primary" }, { "name": "secondary" } // … 3 more],   "tokens": ["{semantic.interactive-primary}", "{semantic.interactive-primary-hover}"] }

Every component and token endpoint on this site reads from the same dtcg-vault/ directory the server scans directly.

This registry is real, and it grows.

108 components and 389 tokens today, across the token graph, its component recipes, and the Paper/Writing pillars — every release adds to the same registry.

See the version history
Important Information

Design System disclosure

This site provides open-source design tokens, documentation, and self-hostable software published by Woodfine Capital Projects Inc. Information here is for general reference only and does not constitute an offer, warranty, or a guarantee of fitness for any particular purpose. Statements regarding planned, intended, or targeted future features are forward-looking and subject to change without notice; they are not undertaken to be updated except as required by law.