Design Systems

Use when the user asks about design system strategy, Figma variables, Figma to code, a design tokens pipeline with Style Dictionary or Tokens Studio, the W3C DTCG token format, governance, component inventory or adoption metrics. Produces the design-side token taxonomy, pipeline and governance model. Not for coding the component library (use frontend-design-system).

45 stars 6 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill design-systems
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/design/design-systems ~/.claude/skills/design-systems

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Design Systems (Design ↔ Code Workflow)

## Purpose
A design system is a product: tokens, components, patterns, documentation and the process that keeps design files and code in sync. This skill defines the token architecture, the automated pipeline from Figma variables to platform code, component specs that engineers can implement without guessing, and the governance that keeps the system alive.

## Agent Protocol

### Trigger
"design system", "design tokens", "Figma variables", "Figma to code", "Style Dictionary", "Tokens Studio", "DTCG", "component spec", "design system governance", "adoption".

### Input Context
- Design tool (Figma variables/styles, Tokens Studio plugin) and where tokens live today.
- Target platforms (web CSS, iOS, Android, Flutter) and theming needs (brands, dark mode, density).
- Team size, consumers (number of products), current pain (drift, duplicated components).

### Output Artifact
Token taxonomy + example token files, pipeline config, component spec template, governance process.

### Response Format
```
Tiers: primitive -> semantic -> component
Source of truth: {Figma variables|tokens repo}
Pipeline: {export step} -> {Style Dictionary build} -> {platform outputs}
Modes/themes: {light, dark, brand-x}
Governance: {owner, contribution flow, release cadence}
```

## Token Architecture

| Tier | Example | Who uses it |
|------|---------|-------------|
| Primitive (option) | `color.blue.600 = #2563eb`, `space.4 = 16px` | Only semantic tokens |
Read the full skill on GitHub

Details

Skill name
design-systems
Path
skills/design/design-systems/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Design Systems skill do?

Use when the user asks about design system strategy, Figma variables, Figma to code, a design tokens pipeline with Style Dictionary or Tokens Studio, the W3C DTCG token format, governance, component inventory or adoption metrics. Produces the design-side token taxonomy, pipeline and governance model. Not for coding the component library (use frontend-design-system).

How do I install the Design Systems skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill design-systems. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Design Systems popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Design Visual Design

45

j4flmao/agent-skills

Use when the user asks about visual design, color palettes, typography and type scales, spacing, layout grids, visual hierarchy, or says the UI looks AI-generated or generic and should look designed. Produces concrete visual decisions and critique. Not for token pipelines (use design-systems) or brand guidelines (use design-brand-identity).

Frontend & Design

Design Motion Design

45

j4flmao/agent-skills

Use when the user asks about motion design, micro-interactions, easing and duration guidelines, Lottie, transition choreography, motion specs or reduced-motion rules. Produces motion principles, timing tokens and handoff specs. Not for coding animations (use frontend-animation).

Frontend & Design

Desktop Gtk

45

j4flmao/agent-skills

Use when the user asks about GTK 4 or GTK 3, GtkWidget, GtkBuilder or Blueprint UI files, GTK CSS, event controllers, GtkListView, gtk-rs or PyGObject apps. Produces GTK application code and UI definitions. Not for GNOME Shell extensions or libadwaita platform integration (use desktop-gnome).

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.