What is design-system?

A set of rules and shared building blocks for keeping a product’s interface consistent, including colors, spacing, components, documentation, and related tools.

Use it to plan a design system, choose formats for shared design values, connect design tools such as Figma to code, and organize component libraries and documentation.

It prevents different teams or products from implementing the same interface elements in different ways. It also gives designers and developers a shared reference for how the interface should look and behave.

design-system — Skill for Claude Code by Tyler-R-Kendrick

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.

Any agent

npx skills add Tyler-R-Kendrick/agent-skills --skill design-system

Clone the repo

git clone --depth 1 https://github.com/Tyler-R-Kendrick/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 57 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/design-system/github.svg)](https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/design-system)

Your own site

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/design-system"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/design-system/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/design-system"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,140 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.

Model	Per session	Once invoked
Fable 5.1	$0.00111	$0.01140
Opus 5	$0.00056	$0.00570
Sonnet 5	$0.00022	$0.00228
Haiku 4.5	$0.00011	$0.00114

Measured 11d ago against content hash fa20bfdfae2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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 · 115 lines

How it starts

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

Design System

Overview

A design system is the single source of truth for an organization's UI — combining design tokens, component libraries, documentation, and tooling into a cohesive ecosystem. It ensures consistency, accelerates development, and bridges the gap between design and engineering.

Architecture Layers

┌─────────────────────────────────────────────────┐
│  Design (Figma)                                 │
│  Variables, components, styles, auto-layout     │
├─────────────────────────────────────────────────┤
│  Tokens (W3C DTCG / Style Dictionary)           │
│  Color, typography, spacing, elevation, motion  │
├─────────────────────────────────────────────────┤
│  Components (React, Vue, Angular, Web Comp.)    │
│  Buttons, inputs, modals, cards, layouts        │
├─────────────────────────────────────────────────┤
│  Documentation (Storybook)                      │
│  Stories, usage guidelines, interaction tests   │
└─────────────────────────────────────────────────┘

Design-to-Code Pipeline

Figma Variables ──► W3C DTCG JSON ──► Style Dictionary ──► CSS / SCSS / iOS / Android
                                                            │
Figma Components ──► Code Connect / Mitosis ──────────────► React / Vue / Angular / Svelte
                                                            │
                                                            ▼
                                                        Storybook
                                                  (catalog + interaction tests)

Token Architecture

Design tokens are the atomic values of a design system — colors, spacing, typography, elevation, motion. They flow through three tiers:

Tier	Example	Purpose
Global	`blue-500: #3b82f6`	Raw palette values
Alias / Semantic	`color-primary: {blue-500}`	Intent-based references
Component	`button-bg: {color-primary}`	Scoped to a specific component

Component Strategy

Read the full file on GitHub · 115 lines

Files

What ships with it

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

11d ago First seen · 115 lines · 111 tokens per session scan A fa20bfdfae2a

Subscribe to this mod's changes

design-system is a skill published in the GitHub repository Tyler-R-Kendrick/agent-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 111 tokens to every session and 1,140 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-31.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

design-system