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/demo-video/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/demo-video)<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/demo-video"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/demo-video/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/demo-video"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/demo-video.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.00167 | $0.02928 |
| Opus 5.5 | $0.00067 | $0.01171 |
| Sonnet 5.5 | $0.00033 | $0.00586 |
| Haiku 4.5 | $0.00017 | $0.00293 |
Grade A, and why
demo-video 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo video pipeline (VHS + recorded voiceover)
Turn a demo script into a narrated MP4 (the user's voiceover synced to a terminal
recording) plus silent GIF/WebM assets for docs. The pipeline lives in
tools/demo/videos/ and is driven by a single manifest.
Core idea — the beat is the unit of sync
VHS has no audio, and human narration timing varies per take. So each demo is split into beats: a chunk of on-screen action + one line of narration. Each beat is rendered to its own silent clip and recorded to its own audio clip; at build time the video's last frame is frozen to match the audio length (plus a short tail). This guarantees the video never outpaces the voice and lets any single beat be re-recorded independently.
manifest ─▶ render.mjs ─▶ silent beat clips + full GIF/WebM
manifest ─▶ record.mjs ─▶ one .wav per beat (teleprompter + mic)
build.mjs ─▶ pad video→audio, mux, concat ─▶ <slug>.narrated.mp4 + .srt/.vtt
Prerequisites
vhs(brew install vhs) andffmpeg/ffprobe(brew install ffmpeg) on PATH.- For CLI/TUI demos the binary must build; the manifest's
prebuildhandles this (mirrorstools/demo/verify-demo.sh).
1. Author or edit a manifest
Manifests are zero-dependency ES modules: tools/demo/videos/<slug>.demo.mjs. Start from
cli-quickstart.demo.mjs. The full
schema is documented in lib/tape.mjs:
export default {
title: "design-data CLI — quickstart",
slug: "cli-quickstart", // filename-safe basename for all outputs
width: 1280, height: 720, fontSize: 22,
theme: "Catppuccin Mocha", typingSpeed: "60ms",
prebuild: ["cargo build --release --manifest-path sdk/Cargo.toml --bin design-data"],
setup: ['export PATH="$PWD/sdk/target/release:$PATH"', "clear"], // hidden per beat
beats: [
{
id: "component", // stable slug → <slug>-component.mp4/.wav
narration: "One sentence spoken over this beat.",
tape: `Type "design-data component button --components-dir packages/design-data/components"
Enter
Wait
Sleep 3s`,
},
],
};
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 · 235 lines · 167 tokens per session scan A 3e82923780f7
demo-video is a skill published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It adds 167 tokens to every session and 2,928 once invoked, about $0.0007 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
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.
styleseed
Build, improve, or inspect UI with StyleSeed. Preserves project design choices and routes setup, layout, tokens, review, rendered verification, and updates through one entry point.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
cicd-integration
Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression, bundle size. Trigger: set up CI, quality gates, automate these checks. Not for running an audit.
codebase-index
Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.