design-system-governance

Enforce token-first and composition-first governance for design system projects.

15|2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/harrychuang/cursor-skills --skill design-system-governance-harrychuang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-governance
Source: https://github.com/harrychuang/cursor-skills/tree/main/design-system-governance
Command: npx skills add https://github.com/harrychuang/cursor-skills --skill design-system-governance-harrychuang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces strict token-first and composition-first governance for design system projects, preventing inconsistencies and ensuring adherence to established principles.

Core Features & Use Cases

  • Automated Convention Detection: Auto-detects token naming, grid systems, animation keyframes, and component libraries.
  • Strict Governance Gates: Implements token and composition gates to halt development before non-compliant changes are made.
  • Universal Design Principles: Applies 10 core design principles to all UI development.
  • Use Case: When building new UI components, use this Skill to ensure they strictly adhere to your design system's token structure and composition rules, preventing hardcoded values and orphaned components.

Quick Start

Use the design-system-governance skill to audit the current project's design token conventions.

Frequently Asked Questions about design-system-governance

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

FAQPage Schema
How do I enforce design system consistency and prevent hardcoded values in my UI components?

Token-first governance works by auto-detecting your project's design token conventions and applying strict gates that halt development before non-compliant changes are made. It ensures all UI components adhere to the established token naming and structure automatically.

How do I audit my project's design token conventions and component library structure?

You can audit design token conventions using automated convention detection. This process auto-detects token naming, grid systems, animation keyframes, and component libraries to identify non-compliant values and enforce strict governance gates across your project.

Do I need Storybook stories for all visual states to enforce composition-first design rules?

Yes, you need Storybook stories for all visual states to enforce composition-first governance. This ensures every component variation is documented and validated against your design system's token structure, preventing orphaned components and maintaining strict adherence to universal design principles.

What is the best way to govern animation and i18n in a design system component library?

The best way to govern animation and i18n is to apply strict token-first and composition-first governance gates. This approach auto-detects animation keyframes and enforces composition rules, ensuring internationalization and page composition adhere to established design tokens and universal principles.

How does a token-first design system handle internationalization and page composition rules?

A token-first design system handles internationalization and page composition by enforcing strict governance gates. It auto-detects your conventions and requires adherence to 10 universal design principles, ensuring all i18n and page layout changes remain consistent with the established token structure.