org.designtxt.tokenCollection

bomberstudios.com

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "A design tokens document following DTCG 2025.10 format. Metadata fields (name, description, createdAt) are provided for human identification. The token tree coexists at the same object level -- each remaining key is a token (has $value) or group (no $value, may contain nested tokens/groups).",
      "key": "any",
      "record": {
        "description": "Root object of a token collection. Metadata fields are explicitly defined. Any additional keys are treated as tokens or groups per the DTCG 2025.10 Format specification.",
        "properties": {
          "createdAt": {
            "description": "Timestamp when this collection was created.",
            "format": "datetime",
            "maxLength": 64,
            "type": "string"
          },
          "description": {
            "description": "Optional description of this token collection's purpose or scope.",
            "maxGraphemes": 1024,
            "maxLength": 4096,
            "type": "string"
          },
          "name": {
            "description": "Human-readable name for this token collection (e.g. 'Brand Tokens', 'My Design System Q3').",
            "maxGraphemes": 256,
            "maxLength": 512,
            "type": "string"
          },
          "resolver": {
            "description": "AT-URI of the org.designtxt.resolver record for this collection. When present, the viewer can offer a context/theme switcher.",
            "format": "at-uri",
            "maxLength": 1024,
            "type": "string"
          }
        },
        "type": "object"
      },
      "type": "record"
    }
  },
  "description": "A record containing a collection of design tokens in DTCG 2025.10 format. The record has typed metadata fields (name, description, createdAt) alongside the token tree. Token/group keys sit at the same level as metadata; atproto ignores unexpected fields, so the token tree passes through without schema-level validation.",
  "id": "org.designtxt.tokenCollection",
  "lexicon": 1
}

Validate Record

Validate a record against org.designtxt.tokenCollection

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:34yvx4hv64znmh2i2fezoyqx
CID
bafyreigp6kezchtzgfclawh3qhtxlbdcu6xgwo4u2zqj5pypvy2uuh4qzu
Indexed At
2026-07-16 14:09 UTC
AT-URI
at://did:plc:34yvx4hv64znmh2i2fezoyqx/com.atproto.lexicon.schema/org.designtxt.tokenCollection

Version History (2 versions)

Similar Lexicons

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A resolver document for multi-context design tokens (theming, breakpoints, accessibility modes). Follows the DTCG Resolver 2025.10 specification. Describes how token sets and contextual modifiers combine to produce reso…

  • XRPC Query to retrieve a design token collection, optionally at a specific subtree path, and optionally with alias references resolved. Implemented at https://xrpc.designtxt.org/xrpc/org.designtxt.getTokens

Lexicon Garden

@