Agent skill

Rampstack Design System Skill: Build or Audit One

The rampstack design-system skill makes an AI coding agent build or audit a design system in five layers, from tokens up to governance, and write an audit report.

Install
/plugin marketplace add rampstackco/claude-skills
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the rampstack design-system skill?

The rampstack design-system skill is one of 103 skills in the rampstackco repository. It has your AI coding agent either build a design system or audit an existing one. It works through five layers, from tokens to governance, and an audit ends as a markdown report you can hand to a team.

Rampstack publishes a catalog of 103 skills in one repository. The one named design-system builds or audits a design system. It wakes when you mention a design system, component library, design tokens, atomic design, Storybook, a Figma library or governance.

The five layers it works through

  • Foundations: the tokens, meaning the raw values everything else draws from.
  • Elements: the atoms built from those tokens.
  • Components: elements combined into reusable parts.
  • Patterns: templates that arrange components into page structures.
  • Documentation and governance: how the system is described, owned and kept current.

The skill's two-tier token example pairs a base token, color-blue-600, with a semantic token, color-text-link. Naming the purpose separately from the raw value is the idea behind the split, and the foundations layer is where it lives.

Build mode and audit mode

  • A new system follows a nine step workflow.
  • An existing system follows a six step audit workflow.
  • The audit result is a markdown report called design-system-audit.md, written in six sections.
  • A dedicated section covers what to do when required data is unavailable, so the agent has a defined fallback.

Who the rampstack skill is for

Best for

  • Teams starting a component library who want layers and governance decided before screens multiply.
  • A design system that has drifted and needs a structured audit with a written report.
  • Any stack. The README names Next.js, WordPress, Shopify, Webflow and plain HTML.

Not for

  • Pulling tokens out of a live site. For that, see extract-design-system.
  • A one-off critique of a single screen. critique fits that job better.
  • Writing component code. The repo lists a separate frontend-component-build skill for that.

Use it with UiChemy

Decide your tokens and component layers here, then build in Figma. UiChemy Figma to WordPress converts that Figma design into a WordPress site, and Composer edits HTML, CSS and JS in Elementor or Gutenberg. Click Get Started on uichemy.com. Token naming is covered in design-token.