Agent skill

Design Systems

by Mindrally in Mindrally/skills

Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries.

Apache-2.0Auto-check passedFrontend & Design

Install Design Systems

skills CLI
$ npx skills add Mindrally/skills --skill design-systems -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mindrally/skills design-systems --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-systems .claude/skills/design-systems && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-systems
GitHub stars
269
Token cost
~1.8k tokens
SKILL.md length
598 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
Apache-2.0

At a glance

Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries.

  • Works in 7 steps: Audit existing UI — Inventory current… → Define design tokens — Establish… → Build foundational components — Create… → …
  • Creating design tokens
  • SKILL.md covers Workflow: Setting Up a Design…, Foundation Elements, Component Architecture and Accessibility Requirements, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design Systems is an agent skill from Mindrally/skills. Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries. Use when creating design tokens, building component libraries, implementing design systems, setting up theming architecture, or establishing UI governance processes.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems and Design tokens. It works with Storybook. The repository describes itself as: 265+ Claude Code skills for every major framework and language. Install with: npx skills add Mindrally/skills. The licence is Apache-2.0.

When your agent uses it

  • Creating design tokens
  • Building component libraries
  • Implementing design systems
  • Setting up theming architecture

Example prompts

  • “/design-systems”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Audit existing UI — Inventory current components, colors, typography, and spacing across the product to identify inconsistencies and…
  2. Define design tokens — Establish primitive tokens (colors, spacing, typography, shadows) as CSS custom properties or a token format (e.g…
  3. Build foundational components — Create atomic components (Button, Input, Text, Icon) that consume design tokens and expose a clear props…
  4. Compose patterns and layouts — Assemble atomic components into higher-order patterns (forms, cards, navigation) with documented usage…
  5. Set up documentation and Storybook — Configure Storybook with stories for every component variant, state, and accessibility annotation…
  6. Integrate testing and governance — Add visual regression tests (e.g., Chromatic), accessibility linting (e.g., axe-core), and a…
  7. Ship and iterate — Publish the library as a versioned package, gather consumer feedback, and run regular accessibility and performance…

What it can do on your machine

Read from SKILL.md and the folder at commit 7682ca7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and css).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design Systems loads about 1.8k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 598 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mindrally/skills at commit 7682ca7, republished under its Apache-2.0 licence (© Mindrally). 598 words, ~1,845 tokens.

Download SKILL.mdSave it as .claude/skills/design-systems/SKILL.md (or your agent's skills folder).
name
design-systems
description
Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries. Use when creating design tokens, building component libraries, implementing design systems, setting up theming architecture, or establishing UI governance processes.
metadata.maintainer
Mindrally
metadata.source
https://github.com/Mindrally/skills

Design Systems Best Practices

Guidelines for creating and maintaining design systems that ensure visual consistency, accessibility compliance, and scalable component architecture across digital products.

Workflow: Setting Up a Design System

  1. Audit existing UI — Inventory current components, colors, typography, and spacing across the product to identify inconsistencies and reusable patterns.
  2. Define design tokens — Establish primitive tokens (colors, spacing, typography, shadows) as CSS custom properties or a token format (e.g., Style Dictionary) that serves as the single source of truth.
  3. Build foundational components — Create atomic components (Button, Input, Text, Icon) that consume design tokens and expose a clear props API with TypeScript types.
  4. Compose patterns and layouts — Assemble atomic components into higher-order patterns (forms, cards, navigation) with documented usage guidelines.
  5. Set up documentation and Storybook — Configure Storybook with stories for every component variant, state, and accessibility annotation. Publish as a living style guide.
  6. Integrate testing and governance — Add visual regression tests (e.g., Chromatic), accessibility linting (e.g., axe-core), and a contribution/review process for new components.
  7. Ship and iterate — Publish the library as a versioned package, gather consumer feedback, and run regular accessibility and performance audits.

Foundation Elements

Color System
  • Define primary, secondary, and accent colors
  • Include semantic colors for success, warning, error, info states
  • Ensure all color combinations meet WCAG contrast requirements
  • Document color usage guidelines and contexts
  • Provide light and dark mode variants
Typography
  • Establish a type scale with consistent ratios
  • Define font families for headings and body text
  • Set line heights and letter spacing standards
  • Document font weights and their usage
  • Ensure readability across screen sizes
Spacing System
  • Define consistent spacing scale (4px, 8px, 16px, 24px, etc.)
  • Create layout primitives for common patterns
  • Document margin and padding conventions
  • Ensure responsive spacing behavior
  • Use CSS custom properties for maintainability
Icons and Imagery
  • Maintain consistent icon style and sizing
  • Define icon grid and stroke weights
  • Document icon naming conventions
  • Optimize assets for web performance
  • Provide multiple formats when needed (SVG, PNG)

Component Architecture

Component Structure
  • Create atomic, reusable components
  • Define clear component APIs (props/attributes)
  • Document variants and states
  • Ensure components are accessible by default
  • Provide clear naming conventions
Show full SKILL.md (246 more words)Show less
Component States
  • Default state
  • Hover state
  • Focus state (keyboard navigation)
  • Active/pressed state
  • Disabled state
  • Loading state
  • Error state
Component Variants
  • Size variants (small, medium, large)
  • Color/theme variants
  • Layout variants
  • Contextual variants

Accessibility Requirements

  • Follow WCAG 2.1 AA guidelines minimum
  • Use semantic HTML elements
  • Provide ARIA labels where needed
  • Ensure keyboard navigation
  • Test with screen readers
  • Maintain color contrast ratios
  • Support reduced motion preferences

Documentation Standards

Component Documentation
  • Purpose and use cases
  • Props/API reference
  • Code examples
  • Do's and don'ts
  • Accessibility notes
  • Related components
Pattern Documentation
  • When to use
  • Anatomy breakdown
  • Behavior specifications
  • Responsive considerations
  • Edge cases

Implementation Guidelines

CSS Architecture
  • Use CSS custom properties for tokens
  • Implement utility classes for common patterns
  • Follow BEM or similar naming convention
  • Ensure specificity is manageable
  • Support theming and customization
Component Libraries
  • Framework-agnostic when possible
  • Tree-shakeable exports
  • TypeScript support
  • Comprehensive test coverage
  • Storybook integration

Governance

Contribution Guidelines
  • How to propose new components
  • Review and approval process
  • Versioning strategy
  • Breaking change policy
  • Deprecation process
Maintenance
  • Regular accessibility audits
  • Performance monitoring
  • Browser compatibility testing
  • Documentation updates
  • Community feedback incorporation

Design Tokens

Token Categories
  • Colors
  • Typography (font sizes, weights, line heights)
  • Spacing
  • Border radius
  • Shadows
  • Breakpoints
  • Animation durations
  • Z-index values
Token Implementation
css
:root {
  /* Colors */
  --color-primary-500: #0066cc;
  --color-neutral-100: #f5f5f5;

  /* Spacing */
  --space-1: 4px;
  --space-2: 8px;
  --space-4: 16px;

  /* Typography */
  --font-size-sm: 0.875rem;
  --font-size-base: 1rem;
  --font-size-lg: 1.125rem;

  /* Shadows */
  --shadow-sm: 0 1px 2px rgba(0, 0, 0, 0.05);
  --shadow-md: 0 4px 6px rgba(0, 0, 0, 0.1);
}
Example: React Button Component Using Design Tokens
tsx
import React from "react";

interface ButtonProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
  variant?: "primary" | "secondary" | "danger";
  size?: "sm" | "md" | "lg";
  loading?: boolean;
}

const sizeStyles: Record<string, React.CSSProperties> = {
  sm: { padding: "var(--space-1) var(--space-2)", fontSize: "var(--font-size-sm)" },
  md: { padding: "var(--space-2) var(--space-4)", fontSize: "var(--font-size-base)" },
  lg: { padding: "var(--space-3) var(--space-6)", fontSize: "var(--font-size-lg)" },
};

export const Button: React.FC<ButtonProps> = ({
  variant = "primary",
  size = "md",
  loading = false,
  disabled,
  children,
  ...props
}) => (
  <button
    style={{
      ...sizeStyles[size],
      backgroundColor: `var(--color-${variant}-500)`,
      color: "var(--color-neutral-100)",
      borderRadius: "var(--radius-md)",
      boxShadow: "var(--shadow-sm)",
      cursor: disabled || loading ? "not-allowed" : "pointer",
      opacity: disabled ? 0.5 : 1,
    }}
    disabled={disabled || loading}
    aria-busy={loading}
    {...props}
  >
    {loading ? "Loading…" : children}
  </button>
);
Example: Storybook Configuration
ts
// .storybook/preview.ts
import type { Preview } from "@storybook/react";
import "../src/tokens.css"; // import design tokens globally

const preview: Preview = {
  parameters: {
    a11y: { element: "#storybook-root" },
    backgrounds: {
      default: "light",
      values: [
        { name: "light", value: "#ffffff" },
        { name: "dark", value: "#1a1a1a" },
      ],
    },
  },
};

export default preview;

Quality Assurance

  • Visual regression testing
  • Accessibility automated testing
  • Cross-browser testing
  • Performance benchmarking
  • Component unit testing
  • Integration testing

When evolving the design system, validate changes against WCAG 2.1 AA, run visual regression tests, and ensure token updates propagate correctly across all consuming applications.

© Mindrally, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in design-systems of Mindrally/skills.

Open the folder on GitHubat commit 7682ca7

Compare with similar skills

Design Systems next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design Systems compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design Systems this skillMindrally/skills269—~1.8kAutomated safety check: PassApache-2.0
Design Systemrampstackco/claude-skills941—~2.4kAutomated safety check: PassMIT
Composer UIdxos/dxos525—~9.3kAutomated safety check: PassCustom licence
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Design SystemOhh-889/skyroc79511 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Design System

    rampstackco/claude-skills

    Build or audit a design system including component library, design tokens, naming conventions, contribution model, and documentation.

    941 GitHub stars~2.4k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Composer UI

    dxos/dxos

    A skill your agent uses when building or styling plugin UI with Composer's design system — the @dxos/react-ui packages.

    525 GitHub stars~9.3k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed
  • Design Dna

    zanwei/design-dna

    Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…

    1.9k GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed

More from Mindrally/skills

All 34 skills in this repo
  • Analytics Data Analysis

    Mindrally/skills

    Best practices for analytics, data analysis, and visualization using Python, pandas, matplotlib, seaborn, and Jupyter notebooks.

    269 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Best practices for AutoML and hyperparameter search with Optuna, Ray Tune, and PyCaret, covering search-space design, validation splits, and leakage prevention.

    269 GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Blender Python Addon

    Mindrally/skills

    Best practices for writing Blender Python add-ons using the bpy API, covering operators, panels, properties, registration, and API-safe scripting.

    269 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices.

    269 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Clean Code

    Mindrally/skills

    Clean, maintainable, human-readable code principles combined with anti-over-engineering discipline: naming, single responsibility, DRY, and scoping changes to exactly what was requested.

    269 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Embedded Stm32

    Mindrally/skills

    Best practices for embedded C/C++ development on STM32 microcontrollers using the HAL, covering peripherals, DMA, interrupts, memory constraints, and hardware-focused testing.

    269 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Questions about Design Systems

What does Design Systems do?

Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries. Design Systems is an agent skill from Mindrally/skills. Comprehensive design system guidelines for building consistent, accessible, and scalable component libraries.

When should I use Design Systems?

Design Systems fits situations like: creating design tokens; building component libraries; implementing design systems; setting up theming architecture.

How do I install Design Systems in Claude Code?

Run `npx skills add Mindrally/skills --skill design-systems -a claude-code`. Or copy the skill folder (design-systems in Mindrally/skills) into .claude/skills/design-systems in your project. Claude Code loads it when a task matches its description.

How do I install Design Systems in Codex?

Run `npx skills add Mindrally/skills --skill design-systems -a codex`. Or copy the skill folder (design-systems in Mindrally/skills) into .agents/skills/design-systems in your project. Codex loads it when a task matches its description.

Can I use Design Systems in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mindrally/skills --skill design-systems -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-systems, .gemini/skills/design-systems, .github/skills/design-systems and .opencode/skills/design-systems in your project.

What does Design Systems need to run?

SKILL.md names no scripts, command-line tools or credentials: Design Systems is instructions for the agent only.

Does Design Systems access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design Systems safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design Systems use?

Design Systems is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design Systems use?

About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design Systems?

Skills that share tags, products or a category with Design Systems: Design System (rampstackco/claude-skills, 941 stars), Composer UI (dxos/dxos, 525 stars), Figma Design System Builder (warpdotdev/warp, 65k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design Systems?

Mindrally (a GitHub organization) maintains it in Mindrally/skills, which has 269 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 8, 2026.

Source: Mindrally/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.