The design system,
written in plain markdown.

Design systems were written for humans, with tooling bolted on. Agentic development inverts that. Soon most consumers of your system will be models, and a system an agent can’t read doesn’t exist for it.

So this one starts from the file. Every token, rule and pattern lives in versioned markdown. Small enough to drop into a context window, explicit enough to be followed, human enough to be argued with in a pull request.

This is the real file, typing itself. Each line a human can read is a value an agent can use. The rest of it stays under wraps until v0.1 ships.

• tokens.md

  Color, type, space and motion as named values with usage rules. The foundation everything sits on.

  drafting
• components.md

  Each component as anatomy, states and do/don’t. Specification comes before implementation.

  drafting
• patterns.md

  Compositions and flows. How components assemble into product without improvisation.

  planned
• agents.md

  The agent contract. Constraints, guardrails and defaults a model must respect when it builds with the system.

  planned

No sync jobs, no plugin lag, no second source of truth. Change the file, and every consumer, human or model, inherits the change on the next read.

1. P·1

   Files over portals

   A documentation site is a rendering, never the source. If it can’t be cloned, grepped and diffed, it’s not the system.

2. P·2

   Constraints are the interface

   A good constraint doesn’t restrict design. It makes bold moves safe. Explicit guardrails are what let an agent build fast without breaking the brand.

3. P·3

   Readable is shippable

   If a rule needs a meeting to be understood, it will be ignored by people and hallucinated by models. Every rule earns one plain sentence.

1. v0.1

   Foundations

   tokens.md with color, type scale, spacing and motion. The values before the components.

   in progress
2. v0.2

   Components & patterns

   components.md and patterns.md, specification-first and implementation-agnostic.

   next
3. v0.3

   The agent contract

   agents.md, the contract that turns the system into an operating constraint for models.

   planned