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.
Borrowing it
Nothing to install: this file belongs to adobe/spectrum-design-data. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adobe/spectrum-design-data/main/.ai/skills/spectrum-diagrams/SKILL.mdgit clone --depth 1 https://github.com/adobe/spectrum-design-dataWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/adobe/spectrum-design-data/spectrum-diagrams)<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/spectrum-diagrams"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/spectrum-diagrams/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/spectrum-diagrams"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/spectrum-diagrams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00106 | $0.02086 |
| Opus 5.5 | $0.00042 | $0.00834 |
| Sonnet 5.5 | $0.00021 | $0.00417 |
| Haiku 4.5 | $0.00011 | $0.00209 |
Grade A, and why
spectrum-diagrams scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spectrum diagrams for docs articles
Turns a real technical structure (code, tokens, spec, pipeline) into a diagram that looks like it belongs next to Spectrum's own docs, and embeds it in an article.
This skill is a workflow on top of the Figma MCP's own skills — it doesn't re-document their tool mechanics. Load those when this skill tells you to.
When to use this
- An article has an
<!-- Illustration: ... -->placeholder comment for a diagram (the established convention in this repo — seeunderstanding-spectrum-tokens.md). - Someone asks for an architecture diagram, flowchart, pipeline, or tiered/cascade
diagram to go in a
docs/site/src/articles/*.mdfile.
Not for: decorative hero illustrations or brand illustration (bell/cloud/lightbulb
style icons). Those come from the real S2 Illustrations Figma library, not
generate_diagram — see Illustration guardrails below. If a
placeholder asks for one, say so and point at the library rather than faking one with
generate_diagram.
Workflow
1. Gather the real structure first
Read the actual code, tokens, or spec the diagram represents before writing any Mermaid. Don't invent services, edges, or tiers to "round out" a diagram — a partial, accurate diagram beats a polished, hallucinated one. If the article prose already describes the structure (tables, code blocks), that prose is the source of truth; walk it node by node.
2. Load /figma-generate-diagram and pick the type
This is mandatory before calling generate_diagram (per the Figma MCP server's own
instructions). It routes you to type-specific guidance and sets universal Mermaid
constraints (no emojis, no \n in labels, reserved words, etc.) — follow it, don't
duplicate it here.
Two shapes come up repeatedly in this repo's articles:
- Real software architecture (services, datastores, queues, external calls) →
the architecture layout:
flowchart LR, every node inside one of the fixed subgraphs (client/gateway/service/datastore/external/async), passuseArchitectureLayoutCode: "FIGMA_DIAGRAM_2026". - Conceptual structure (token tiers, a cascade/precedence model, a pipeline of
stages) → a plain
flowchart(see the Figma skill'sflowchart.mdreference). No subgraph-ID constraint applies here — use whatever grouping reads clearly.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 163 lines · 106 tokens per session scan A df56e318452b
spectrum-diagrams is a skill published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It adds 106 tokens to every session and 2,086 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.
Other skills, from other repositories
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.