design-data-agent

design-data agent skill

@adobe/design-data-agent-mcp provides in-process wasm tools for validating, querying, resolving, diffing, and authoring spec-conformant tokens and components from any dataset on the local filesystem.

Set two path variables once and reference them throughout:

export DESIGN_DATA_PATH=./packages/design-data/tokens
export DESIGN_DATA_SPEC_PATH=./packages/design-data

For Spectrum tokens with zero setup (embedded snapshot), use the design-data skill instead — this skill targets custom or repo-local datasets.

Bootstrap

Add @adobe/design-data-agent-mcp to your .cursor/mcp.json:

{
  "mcpServers": {
    "design-data-agent": {
      "command": "npx",
      "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
      "env": {
        "DESIGN_DATA_PATH": "./packages/tokens/src",
        "DESIGN_DATA_COMPONENTS": "./packages/design-data/components",
        "DESIGN_DATA_FIELDS": "./packages/design-data/fields"
      }
    }
  }
}

Adjust paths to match your dataset layout. Pin @latest — the embedded Spectrum snapshot is baked into the wasm at build time and travels with the package version, so there's no separate data update to run, but plain npx -y <pkg> (no tag) can reuse a cached older build.

---

Session start — call primer first

Call primer at the start of every session that touches design data. It returns the active dimensions, component list, taxonomy fields, and token count — structural context that scopes all subsequent lookups. No inputs required.

---

Token lookup

Resolve a token to its literal value — resolve_token

Required: property (string) — e.g. "accent-background-color-default" Optional: colorScheme ("light" or "dark"), scale ("desktop" or "mobile"), contrast ("regular" or "high")

Query tokens by filter expression — query_tokens

Required: filter (string)

Valid filter keys: property, component, variant, state, colorScheme, scale, contrast, uuid, $schema.