design-system
Builds scalable design systems with tokens, theming, and component architecture. Use when creating design token hierarchies, theming systems, component variant patterns, or accessibility foundations. Use for design tokens, CVA variants, dark mode, multi-brand theming, Radix headless UI, Storybook documentation, and governance.
- Installs
- 147
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/oakoss/agent-skills --skill design-system- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads design-system automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Design System
Overview
Single source of truth for visual consistency at scale — a shared language between design and engineering. Covers token architecture, theming infrastructure, component API patterns, accessibility compliance, and governance workflows.
Design systems are not component libraries alone. They unify tokens, patterns, documentation, and contribution processes so teams build once and maintain once.
Quick Reference
| Area | Pattern | Key Points |
|---|---|---|
| Token hierarchy | Primitive > Semantic > Component | Never reference primitives in components; semantic layer is themable |
| Dark mode | Swap semantic tokens via data-theme | Use off-white/dark-gray, not pure white/black |
| Multi-brand theming | Override semantic tokens per brand | Apply via CSS custom properties at runtime |
| Tailwind v4 | @theme block in CSS (no config file) | CSS-first configuration replaces tailwind.config.js |
| CVA variants | cva() for variant + size combinations | Type-safe with VariantProps; pair with cn() utility |
| Compound components | Modal.Header, Modal.Body sub-parts | Composition over configuration; shared context for implicit state |
| Headless UI | Radix primitives + Tailwind classes | Accessibility built-in; bring your own styles |
| Focus management | focus-visible:ring-2 on all controls | 2px solid outline with offset; visible on keyboard only |
| Reduced motion | prefers-reduced-motion media query | Near-zero duration for all transitions and animations |
| Style Dictionary | JSON tokens to CSS/iOS/Android | outputReferences: true preserves token chain |
| Storybook | Stories + autodocs + a11y addon | Visual documentation with accessibility audit built in |
| Governance | Semver for tokens and components | Breaking = removed props/tokens; minor = new additions |
Common Mistakes
| Mistake | Correct Pattern |
|---|---|
Primitive tokens in components (blue-500) | Reference semantic tokens (interactive-primary) that map to primitives |
| Skipping focus states on interactive elements | Add focus-visible:ring-2 on every button, link, and input |
Body text set to gray-400 | Use gray-600 or darker to meet 4.5:1 WCAG AA contrast |
| Circular token references between layers | Tokens flow one direction: primitive > semantic > component |
Ignoring prefers-reduced-motion | Wrap all animations in a reduced-motion media query |
Using scale() transforms for hover | Use translateY(-1px) and shadow changes to avoid layout shift |
| Hardcoded hex/px values in component files | All visual values come from semantic or component tokens |
| Deep CSS nesting for theme overrides | Override CSS custom properties at the semantic layer |
| Theme flash on page load (FOUC) | Inject synchronous theme script in <head> before body renders |
| Flat token list without layers | Organize into primitive, semantic, and component tiers |
Delegation
- Audit codebase for hardcoded values that should be tokens: Use
Exploreagent - Migrate a component library to a token-based design system: Use
Taskagent - Plan a multi-brand theming architecture: Use
Planagent - Review accessibility compliance across components: Use
Taskagent
If the
motionskill is available, delegate animation token integration and motion design patterns to it.
References
- Design Tokens — three-layer hierarchy, CSS custom properties, TypeScript definitions, naming conventions
- Theming — dark mode, theme provider, multi-brand, Tailwind v4, SSR flash prevention
- Color and Typography — 60-30-10 rule, contrast requirements, type scale, fluid typography
- Component Architecture — CVA variants, compound components, headless UI, polymorphic rendering
- Accessibility — WCAG compliance, keyboard navigation, ARIA patterns, screen reader testing
- Motion and Layout — animation tokens, reduced motion, spacing grid, elevation system
- Tooling — Style Dictionary, Storybook, component testing, visual regression
- Governance — versioning, deprecation, contribution workflow, component lifecycle
- Troubleshooting — common issues, dark mode fixes, token sprawl, pre-delivery checklist
FAQ
What does the design-system skill do?
Builds scalable design systems with tokens, theming, and component architecture. Use when creating design token hierarchies, theming systems, component variant patterns, or accessibility foundations. Use for design tokens, CVA variants, dark mode, multi-brand theming, Radix headless UI, Storybook documentation, and governance.
How do I install design-system?
Run npx skills add https://github.com/oakoss/agent-skills --skill design-system in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/design-system/ (personal) or .claude/skills/design-system/ (project).
Which AI agents can use design-system?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is design-system safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains design-system?
It is published by oakoss in oakoss/agent-skills. It has 147 recorded installs.
More from oakoss/agent-skills
ui-ux-polish
oakoss/agent-skills
Iterative UI/UX polishing workflow for web applications. Use when improving visual polish, refining desktop and mobile UX separately, running iterative enhancement cycles, applying design patterns like glassmorphism or bento grids, or auditing accessibility and WCAG compliance. Use for Stripe-level visual quality, responsive optimization, and design system alignment.
playwright
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
coolify
oakoss/agent-skills
Coolify self-hosted PaaS for deploying applications, databases, and services via REST API and Git integration. Covers API authentication, deployment triggers, build packs (Nixpacks, Dockerfile, Compose), CI/CD with GitHub Actions webhooks, environment management, and Traefik proxy configuration. Use when deploying apps to Coolify, triggering deployments via API, configuring build packs, setting up GitHub Actions CI/CD pipelines, managing environment variables, or troubleshooting deployment failures.
application-security
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
find-skills
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
drizzle-orm
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.