Design data, including design tokens, component schemas, and tooling for Spectrum, Adobe's design system.
adobe/spectrum-design-data is a monorepo containing the design tokens, component schemas, specifications, and related datasets that define Adobe's Spectrum design system; a monorepo keeps these related packages in one repository. It is for Adobe Spectrum SDK and tooling developers who need canonical design-system data and validation artifacts. The catalogue add-ons provide workflows and integrations for working with this design data.
This repository also configures its own agents. See what spectrum-design-data tells them →
MCP server Claude CodeCodexCursor +2 ✓ vendor
One of 6 in .mcp.json
MCP server "tuiwright" as configured in adobe/spectrum-design-data. Launched with tuiwright --config tuiwright.toml.
MCP server Claude CodeCodexCursor +2 ✓ vendor
One of 6 in .mcp.json
MCP server "figma", hosted remotely at mcp.figma.com, as configured in adobe/spectrum-design-data.
MCP server Claude CodeCodexCursor +2 ✓ vendor
One of 6 in .mcp.json
MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm. Runs locally from the @adobe/design-data-agent-mcp npm package. Needs 5 environment variables to run.
MCP server Claude CodeCodexCursor +2 ✓ vendor
One of 6 in .mcp.json
MCP server "scout" as configured in adobe/spectrum-design-data. Launched with scout mcp.
MCP server Claude CodeCodexCursor +2 ✓ vendor
One of 6 in .mcp.json
MCP server "ferrograph" as configured in adobe/spectrum-design-data. Launched with /bin/sh -c cd sdk && exec ferrograph mcp. Needs 1 environment variable to run.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: