design-data-corpus

design-data-corpus is a cursor rule for Cursor from adobe/spectrum-design-data. It costs 0 tokens per session (255 once invoked), scanned A, original, Apache-2.0.

Repository instructions for editing canonical design-data JSON, including design tokens, fields, registries, and components.

In plain words
What is it for?
Use them when changing files under packages/design-data/. They cover validation, code generation, legacy names, and adding a changeset for user-facing changes.
Why use it?
They help keep the source data, generated SDK data, validation, naming, and release notes consistent when design data changes.

Cursor rule for Cursor ✓ vendor

Written for Cursor: installed under .cursor/.

Good fit Use them when changing files under packages/design-data/. They cover validation, code generation, legacy names, and adding a changeset for user-facing changes.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/adobe/spectrum-design-data/design-data-corpus
About the project

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.

adobe/spectrum-design-data · 156 stars · on GitHub · opensource.adobe.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/adobe/spectrum-design-data

Made for: Cursor.

Wrote 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.

agentmods badge for design-data-corpus

README.md
[![agentmods](https://agentmods.dev/badge/rules/adobe/spectrum-design-data/design-data-corpus/github.svg)](https://agentmods.dev/rules/adobe/spectrum-design-data/design-data-corpus)
Your own site
<a href="https://agentmods.dev/rules/adobe/spectrum-design-data/design-data-corpus"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/design-data-corpus/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.

agentmods 80×15 button for design-data-corpus

Your own site · 80×15
<a href="https://agentmods.dev/rules/adobe/spectrum-design-data/design-data-corpus"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/design-data-corpus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 255 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00255
Opus 5.5 $0.00000 $0.00102
Sonnet 5.5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 2d ago against content hash 7843562d6599, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-data-corpus 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 2d 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.

.cursor/rules/design-data-corpus.mdc · 18 lines

What it actually says

Canonical design data

  • packages/design-data/ is the source of truth for token data. sdk/core embeds it at compile time, so changes require moon run sdk:codegen and moon run sdk:codegen-check.
  • Validate edits with moon run design-data:validate.
  • Reuse existing registry vocabulary (fields, variants, anatomy parts) before adding new ids. Check lifecycle.deprecatedIn and lifecycle.replacedBy on legacy tokens before deciding between new vocabulary and a name.legacyKey pin.
  • Preserve obsolete legacy names with explicit name.legacyKey pins instead of generalized exceptions.
  • Do not change canonical values to work around exporter or tooling gaps.
  • Token and registry changes are user-facing: add a changeset for @adobe/spectrum-design-data.
Changes

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.

  1. 2d ago First seen · 18 lines · 0 tokens per session scan A 7843562d6599

Subscribe to this mod's changes

design-data-corpus is a cursor rule published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 255 tokens. 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.