Design System

Govern and validate design-system changes. Use when tokens, typography, spacing, iconography, themes, or style aliases need repository-grounded evidence.

9 stars 4 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill design-system
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/frontend-ui/design-system ~/.claude/skills/design-system

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 System

## Philosophy
- Keep the skill focused on the decision and workflow the user actually requested.
- Preserve important context through progressive disclosure instead of trimming it away.
- Prefer repo-local contracts, wrappers, and validation before generic advice.

## When To Use
- The user asks about tokens, typography, spacing, iconography, theme variables, or style aliases.
- A change touches design-system packages, token layers, generated styles, or governance docs.
- UI consistency needs repository-grounded evidence before implementation.

## Avoid
- Backend, MCP, or infra-only work with no design-system impact.
- One-off visual tweaks that do not touch shared styling contracts.
- Inventing token names without checking canonical sources.

## Inputs
- user goal
- target package or component
- token layer
- theme constraints
- canonical design docs

## Outputs
- design-system finding or patch
- canonical file evidence
- layer impact
- validation commands
- open tradeoffs
- Schema-bound outputs include schema_version.

## Workflow
- Start with 2-3 focused surfaces before expanding scope.
- Load the smallest canonical design-system surface that can answer the request.
- Identify whether the change belongs to brand, alias, mapped, component, or documentation layers.
- Prefer existing tokens, aliases, primitives, and governance rules before proposing additions.
- Explain impact across generated outputs and consumers when shared contracts change.
Read the full skill on GitHub

Details

Skill name
design-system
Path
Skills/frontend-ui/design-system/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Design System skill do?

Govern and validate design-system changes. Use when tokens, typography, spacing, iconography, themes, or style aliases need repository-grounded evidence.

How do I install the Design System skill?

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

Is Design System popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

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