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/tui-verify/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/tui-verify)<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/tui-verify"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/tui-verify/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/tui-verify"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/tui-verify.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.00124 | $0.02537 |
| Opus 5.5 | $0.00050 | $0.01015 |
| Sonnet 5.5 | $0.00025 | $0.00507 |
| Haiku 4.5 | $0.00012 | $0.00254 |
Grade A, and why
tui-verify 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TUI verification (3-tier strategy)
The design-data TUI (sdk/tui) has a purpose-built verification stack. Choose the
lowest tier that answers your question — Tier 1 is fastest and most exact, Tier 3 is
the only one that catches visual/glyph issues.
Tier 1 render_to_buffer / TestBackend ← deterministic, no terminal, CI backbone
Tier 2 rmux + capture-pane ← real binary, live screen text
Tier 3 asciinema + agg / Ghostty ← pixel image for glyph/colour verification
Prerequisites
- All tiers:
cargo build -p design-data-cli --release(ormoon run :build) so thedesign-databinary is on PATH / insdk/target/release/. - Tier 2:
rmux0.3.x on PATH (brew install rmux). - Tier 3 (asciinema):
asciinema3.x +aggon PATH (brew install asciinema agg). - Tier 3 (Ghostty): Ghostty 1.3.0+, macOS Screen Recording permission granted to the
controlling terminal, and
GetWindowID(brew install smokris/getwindowid/getwindowid).
1. Tier 1 — in-process buffer assertions (default)
render_to_buffer(&mut model, w, h) builds a ratatui TestBackend at an exact size,
draws once, and returns the Buffer for cell-level assertions. No terminal emulator.
All 200+ existing tests use this pattern.
Run the full suite (always start here):
cargo test -p design-data-tui # or: moon run :test
Add a targeted assertion — follow the patterns in
references/tier1-test-api.md
(source: sdk/tui/tests/render.rs, sdk/tui/tests/common/mod.rs):
use common::{render_to_buffer, make_graph_with_tokens, update_ctx};
#[test]
fn my_new_feature_renders_label() {
let graph = make_graph_with_tokens(&["accent-color"]);
let ctx = update_ctx(&graph);
let mut model = Model::new();
update(&mut model, Message::PaletteSubmit("query property=accent-color".into()), &ctx);
let buf = render_to_buffer(&mut model, 80, 24);
// assert specific cell or scan rows:
assert_eq!(buf.cell((0, 0)).unwrap().symbol(), "▶");
}
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 · 241 lines · 124 tokens per session scan A fcfaae5d58a0
tui-verify is a skill published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 2,537 once invoked, about $0.0005 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
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
schema-validator
Validate token files structurally against DTCG 2025.10 (including resolvers), Style Dictionary 3 to 5 or Tokens Studio: parse errors, $type/$value, name rules, broken or circular aliases. Trigger: validate token JSON, DTCG compliance, are my token files valid. Naming or architecture: token-audit.
fmcp-ds-audit-orchestrator
Figma ekranlarını 5 kategori açısından platform-agnostic denetler (DS compliance / a11y / drift / visual QA / impact). Read-only çalışır; bulguları raporlar, düzeltmeleri sadece önerir — mutation için onay + ayrı agent. Her platformda çalışır. Condensed-first: Essentials bölümü %80 case'i kapsar, Advanced sadece edge…
design-fidelity-verify
Prove a running app matches its design spec by measuring rendered values, not eyeballing a screenshot. Use when the user says "verify the design", "is this pixel-perfect", "check against Figma", "does the app match the design", or "design QA this screen". Runs a bounded vision+numeric loop over web or mobile…
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…
seed-verify-figma-mcp-transports
A verification tool for Figma MCP tools that runs the same request through REST and WebSocket connections and compares the answers. MCP is a way for an AI agent to call external tools; REST and WebSocket are two ways to communicate with a service.