design-system

design-system is a skill for Claude Code from rampstackco/claude-skills. It costs 117 tokens per session (2,088 once invoked), scanned A, original, MIT.

A shared set of visual rules, reusable interface parts, and documentation for building digital products consistently. It can cover design tools, code libraries, naming, and how the team maintains them.

In plain words
What is it for?
Use it to create or audit a design system, define design tokens such as colors and spacing, organize a component library, and set contribution rules.
Why use it?
It reduces duplicated or inconsistent components and gives a team a common way to design and build interfaces.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rampstack-skills plugin — 103 skills shipped together

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.

agentmods
npx agentmods add skills/rampstackco/claude-skills/design-system
Any agent
npx skills add rampstackco/claude-skills --skill design-system
Clone the repo
git clone --depth 1 https://github.com/rampstackco/claude-skills

Made for: Claude Code.

Or install rampstack-skills, the plugin that ships this one along with the rest of its 103 skills.

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-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/rampstackco/claude-skills/design-system.svg)](https://agentmods.dev/skills/rampstackco/claude-skills/design-system)
Your own site
<a href="https://agentmods.dev/skills/rampstackco/claude-skills/design-system"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/design-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00117 $0.02088
Opus 5 $0.00059 $0.01044
Sonnet 5 $0.00023 $0.00418
Haiku 4.5 $0.00012 $0.00209

Measured 6d ago against content hash d5bff103c6fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

design-system 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.

skills/design-system/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design System

Build, evolve, or audit a design system. Stack-agnostic in principle. Implementation is stack-specific (Figma, Storybook, code library, etc.) but the structure and governance principles transfer.

This skill is for building the system. For applying a system to specific pages or components, use design-standards. For brand visual identity, use brand-identity.


When to use

  • Building a design system from scratch
  • Auditing an existing system for gaps or fragmentation
  • Defining design tokens at the system level
  • Structuring a component library
  • Establishing contribution and governance models
  • Migrating from ad-hoc components to a documented system

When NOT to use

  • Designing a single page or component (use design-standards)
  • Brand identity work (use brand-identity)
  • Component-level frontend implementation (use frontend-component-build)
  • Pure design documentation for marketing (use brand-style-guide)

Required inputs

  • The brand identity (tokens, voice, imagery direction)
  • The product surfaces the system needs to support (web, mobile, marketing, app, internal tools)
  • The team and its working tools (Figma, code framework, doc platform)
  • Existing components, even if undocumented
  • Constraints (accessibility requirements, performance targets, browser support)

If brand identity is undefined, run brand-identity first.


The framework: 5 layers

A complete design system has five layers, stacked. Each layer feeds the layer above.

1. Foundations (tokens)

The atomic decisions. Color, type, spacing, radius, shadow, motion, breakpoints.

Why this layer matters:

  • Tokens are the source of truth for everything above
  • Token changes propagate everywhere automatically
  • Without tokens, the system has no foundation

Output:

  • A documented token set (see design-standards/references/design-tokens-template.md)
  • Token implementation in code (CSS variables, JS objects, Style Dictionary, etc.)
  • Token implementation in Figma (variables and styles)
  • A primer doc explaining what tokens to use when

Read the full file on GitHub · 209 lines

Files

What ships with it

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

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. 6d ago First seen · 209 lines · 117 tokens per session scan A d5bff103c6fc

Subscribe to this mod's changes

design-system is a skill published in the GitHub repository rampstackco/claude-skills (822 stars, last pushed 8d ago), licensed MIT. It adds 117 tokens to every session and 2,088 once invoked, about $0.0006 per session on Opus 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-08-30.