designsystemdocspec.org valid

Design System Doc Spec (DSDS)

A machine-readable format for design system documentation. DSDS structures a design system as a graph of entries (systems, components, tokens, themes, and custom kinds) and sections (definitions, guidelines, steps, and freeform content) for humans, parsers, and agents.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:30:28.661Z. Cached copy · Source on designsystemdocspec.org

# Design System Doc Spec (DSDS)

> A machine-readable format for design system documentation. DSDS structures a design system as a graph of entries (systems, components, tokens, themes, and custom kinds) and sections (definitions, guidelines, steps, and freeform content) for humans, parsers, and agents.

This site documents DSDS, a versioned JSON Schema. Every page below has an HTML version (for people) and a plain-markdown mirror at the same path with a `.md` extension (e.g. `/quickstart.md`, `/schema.md`) — the full content as text, no HTML/JS to parse. The Schema page's markdown includes every definition's field names, types, and requiredness; the bundled schema below is the single-file version of the same data.

## Machine-readable schema

- [manifest.json](https://designsystemdocspec.org/manifest.json): the typed machine index — every entry kind and section kind, with links to each one's page, markdown and schema. Start here.
- [Bundled schema, v0.23.0](https://designsystemdocspec.org/v0.23.0/dsds.bundled.yaml): every definition in one file
- **Per-definition markdown**: 23 small files, one per schema definition, a few KB each and in the schema's own field order — e.g. [entries-component](https://designsystemdocspec.org/schema/entries-component.md) or [common-ref](https://designsystemdocspec.org/schema/common-ref.md). Fetch one of these to learn a single definition instead of the whole bundle; manifest.json lists all of them under `definitions`.
- [llms-small.txt](https://designsystemdocspec.org/llms-small.txt): a primer of about 5k tokens - the core model, the field and kind lists, one worked example, and how to validate. Read this first if you're short on context
- [llms-full.txt](https://designsystemdocspec.org/llms-full.txt): every guide's full text plus the bundled schema, in one file for one-request ingestion
- [AGENTS.md](https://designsystemdocspec.org/AGENTS.md): how to consume these docs as an agent — where to start, what's normative, how to self-check your work
- [sitemap.xml](https://designsystemdocspec.org/sitemap.xml): every page on this site

## Guides

- [Conformance — DSDS 0.23.0](https://designsystemdocspec.org/conformance): What it means to follow the DSDS spec: the four kinds of conforming thing, the three ways a rule is checked, and every rule. ([markdown](https://designsystemdocspec.org/conformance.md))
- [Examples — DSDS 0.23.0](https://designsystemdocspec.org/examples): Every validated example document DSDS ships, browsable by category: base documents, standalone entries, quickstart snippets, interop pairs, and the negative-test corpus. ([markdown](https://designsystemdocspec.org/examples.md))
- [Interoperability — DSDS 0.23.0](https://designsystemdocspec.org/interoperability): Every format DSDS is built to sit alongside — DTCG, CEM, CSF/Storybook, source files, tests and lint rules, standards, design tools and packages — with the field that points at each and a worked example. ([markdown](https://designsystemdocspec.
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Design. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=designsystemdocspec.org · GET /v1/domain/designsystemdocspec.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for designsystemdocspec.org:
1. POST https://agentwebmap.com/v1/sites/designsystemdocspec.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://designsystemdocspec.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/designsystemdocspec.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/designsystemdocspec.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.