design-system-starter

Define design tokens, component architecture, and WCAG 2.1 AA documentation templates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kamelmh/opencode --skill design-system-starter-kamelmh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-starter
Source: https://github.com/kamelmh/opencode/tree/main/skills/design-system-starter
Command: npx skills add https://github.com/kamelmh/opencode --skill design-system-starter-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you stop reinventing UI every sprint by providing a structured approach to creating and evolving a consistent design system across tokens, components, theming, accessibility, and documentation.

Core Features & Use Cases

  • Design tokens (primitives + semantic): Define color, typography, spacing, radius, and shadow scales with a W3C design-tokens-compatible JSON structure.
  • Atomic component architecture: Plan component inventories and structures using atoms, molecules, organisms, templates, and pages with TypeScript-first patterns.
  • Accessibility-first (WCAG 2.1 AA): Apply keyboard, ARIA, focus management, and contrast-guideline practices throughout components and documentation.
  • Theming & dark mode: Provide theming approaches (CSS variables, Tailwind dark utilities, or ThemeProvider patterns) for light/dark support.
  • Documentation templates and checklists: Generate component docs (props, variants, examples, a11y notes) and use an audit checklist for adoption and maintenance.

Quick Start

Create a design system for my React app with dark mode support and WCAG 2.1 AA accessibility.

Frequently Asked Questions about design-system-starter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a design system with design tokens and WCAG 2.1 AA accessibility?

To create a design system with design tokens and WCAG 2.1 AA accessibility, define W3C-compatible token scales for color and typography, then apply atomic component architecture with keyboard, ARIA, and contrast guidelines throughout.

What is the best way to structure a React component library using atomic design?

The best way to structure a React component library using atomic design is organizing components into atoms, molecules, organisms, templates, and pages with TypeScript-first patterns to ensure maintainability and scalable UI architecture.

How do I implement dark mode theming using CSS variables and design tokens?

Implement dark mode theming using CSS variables and design tokens by defining semantic color scales in a W3C-compatible JSON structure, then applying theming approaches like CSS variables or ThemeProvider patterns for light/dark support.

Can I use this design system approach to audit existing UI components for WCAG compliance?

Yes, you can use this design system approach to audit existing UI components for WCAG compliance by applying the provided accessibility checklist to evaluate contrast, keyboard interactions, ARIA usage, and focus management against WCAG 2.1 Level AA standards.

What design tokens are needed for a production-ready UI system?

Design tokens needed for a production-ready UI system include primitive and semantic scales for color, typography, spacing, radius, and shadows, structured in a W3C design-tokens-compatible JSON format for consistent application across components.

How do I generate documentation templates for a design system component library?

Generate documentation templates for a design system component library by creating structured docs that outline component props, variants, usage examples, and accessibility notes, supplemented by an audit checklist for ongoing maintenance and adoption.