design-foundation

Document design tokens, components, and governance for scalable design systems.

29|6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/sanky369/vibe-building-skills --skill design-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-foundation
Source: https://github.com/sanky369/vibe-building-skills/tree/main/skills/frontend-design/design-foundation
Command: npx skills add https://github.com/sanky369/vibe-building-skills --skill design-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often struggle with inconsistency and scale when building products without a formal foundation, leading to duplicated work and visual drift.

Core Features & Use Cases

  • Token-based design foundation: Define global tokens for color, typography, spacing, and accessibility to ensure consistency across products.
  • Governance and documentation: Establish design principles, guidelines, and a process for adding new tokens and components.
  • Component library scaffolding: Outline architecture and patterns to enable reusable components and faster delivery.
  • Tailwind integration: Provide a token-driven Tailwind config to align styling decisions with tokens.

Quick Start

Start by outlining your design principles, then define color, typography, and spacing tokens, and document a governance process for token updates.

Frequently Asked Questions about design-foundation

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

FAQPage Schema
How do I create a design system with tokens and components?

A design system formalizes scalable foundations by documenting design tokens for color, typography, and spacing, establishing governance rules, and scaffolding reusable components. Start by defining design principles, then create token taxonomy and document the process for updates.

What's the best way to ensure design consistency across products?

Token-based design foundations ensure consistency by centralizing color, typography, spacing, and accessibility definitions as global tokens. Document these tokens with governance guidelines and integrate them into your component library and Tailwind configuration.

Can I use Tailwind with a design token system?

Yes. Tailwind integrates directly with token-driven design foundations through configuration files that align styling decisions with your defined tokens, enabling consistent utility-first styling across your design system.

How do I document accessibility in a design system?

Accessibility in design systems is documented through token taxonomy that includes accessibility considerations alongside color, typography, and spacing definitions. Establish governance guidelines that enforce accessible choices throughout your component library.

What governance process should guide adding new design tokens?

Governance establishes design principles and documented processes for token creation and updates. Define who can propose tokens, criteria for approval, and how new tokens integrate with existing color, typography, and spacing token families.

Why do design systems prevent visual drift and duplicated work?

Formalized design foundations with token documentation and component library scaffolding eliminate inconsistency by providing single sources of truth. Teams reference centralized tokens and reusable components instead of creating isolated solutions.