agentleFS
dylantarredylantarre/design-system-skills/skills/getting-started/SKILL.md

getting-started

Skill50 starsChanged 11 months agoMITView on GitHub

Introduction to the design system skills plugin. Use when first installing the plugin, exploring available skills, or planning a design system implementation.

32 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Building a new design system?: Start here:

    line 14
  2. Very specific:

    Token foundation: Use design-tokens-structure to plan your architecture

    line 16
  3. Very specific:

    Colors: Use color-scale to generate your palette

    line 17
  4. Very specific:

    Spacing/Typography: Use spacing-scale and type-scale

    line 18
  5. Very specific:

    Components: Use your framework skill (react, vue, svelte, angular)

    line 19
  6. Distinctive:

    Learn a concept: Ask about tokens, theming, accessibility

    line 170

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Getting Started with Design System Skills

Overview

This plugin provides 28 skills for building design systems: token generators, component patterns, accessibility guidance, framework integrations, and tool workflows. Each skill is a focused guide Claude uses to help you implement specific parts of a design system.

Quick Start

Building a new design system? Start here:

  1. Token foundation: Use design-tokens-structure to plan your architecture
  2. Colors: Use color-scale to generate your palette
  3. Spacing/Typography: Use spacing-scale and type-scale
  4. Components: Use your framework skill (react, vue, svelte, angular)

Adding to an existing project? Jump to the skill you need:

TaskSkill
Add dark modedark-mode
Fix contrast issuescolor-contrast
Improve animationsanimation-principles + motion-scale
Set up Storybookstorybook
Multi-platform tokensstyle-dictionary

Available Skills

Tokens (10 skills)

Generate design tokens in CSS, Tailwind, or JSON:

SkillPurpose
color-scaleOKLCH color palettes from brand colors
spacing-scaleMargin/padding/gap token scales
type-scaleTypography with modular ratios
shadow-scaleElevation and depth tokens
radius-scaleBorder radius tokens
breakpointsResponsive breakpoint tokens
motion-scaleAnimation duration and easing
z-index-scaleLayering/stacking tokens
design-tokens-structureToken architecture (primitive → semantic → component)
responsive-typographyFluid type with clamp()

Patterns (6 skills)

Implementation patterns for common challenges:

SkillPurpose
dark-modeTheme switching with semantic tokens
compound-componentsRadix/Headless UI patterns
icon-systemSVG sprites and icon components
layout-primitivesStack, Cluster, Grid, Sidebar
animation-principlesDisney's 12 principles for UI

Frameworks (4 skills)

Framework-specific component patterns:

SkillPurpose
reactReact + TypeScript components
vueVue 3 + Composition API
svelteSvelte 5 + runes
angularAngular + signals

Tools (4 skills)

Design tool and build integrations:

SkillPurpose
figmaFigma Variables and Tokens Studio
storybookComponent documentation
framerFramer token integration
style-dictionaryMulti-platform token transformation

Accessibility (3 skills)

WCAG compliance and a11y patterns:

SkillPurpose
color-contrastWCAG contrast validation
focus-statesKeyboard focus indicators
aria-patternsARIA for interactive components

Documentation (2 skills)

Generate documentation:

SkillPurpose
token-docsDesign token documentation
component-docsComponent API documentation

Recommended Paths

Path A: New Design System

1. design-tokens-structure  → Plan your token architecture
2. color-scale              → Generate color palette
3. spacing-scale            → Generate spacing tokens
4. type-scale               → Generate typography tokens
5. shadow-scale             → Generate elevation tokens
6. dark-mode                → Add theme support
7. [framework skill]        → Build components
8. storybook                → Document components

Path B: Add Design Tokens to Existing Project

1. design-tokens-structure  → Understand token layers
2. color-scale              → Convert existing colors to tokens
3. spacing-scale            → Standardize spacing
4. style-dictionary         → Set up build process

Path C: Improve Accessibility

1. color-contrast           → Audit and fix contrast
2. focus-states             → Add visible focus indicators
3. aria-patterns            → Fix interactive components

Path D: Cross-Platform Design System

1. design-tokens-structure  → Plan architecture
2. style-dictionary         → Multi-platform output
3. figma                    → Sync with design tool

How Skills Work

Each skill provides:

  1. When to use: Scenarios that trigger the skill
  2. Quick reference: Tables and cheat sheets
  3. The process: Step-by-step workflow
  4. Implementation checklist: Trackable progress (for complex skills)
  5. Code examples: CSS, Tailwind, JSON, framework-specific

Skills output in multiple formats:

  • CSS custom properties: --color-primary: #3b82f6
  • Tailwind config: theme.extend.colors.primary
  • JSON tokens: Design token format for tools

Tips for Best Results

  1. Be specific: "Generate a blue color scale" → uses color-scale
  2. Mention format: "in Tailwind format" → gets Tailwind config output
  3. Chain skills: "Create spacing tokens then document them" → uses spacing-scale + token-docs
  4. Reference existing: "Match my existing token structure" → adapts to your patterns

Getting Help

  • Find a skill: Describe what you're trying to do
  • Learn a concept: Ask about tokens, theming, accessibility
  • Debug issues: "Why isn't my dark mode working?"
  • Best practices: "What's the best way to structure tokens?"

This plugin is maintained by buoy.design.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.