design-system-forge

Define design tokens, base UI components, and governance artifacts with automated documentation.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/ricardohg1998-create/Plantilla-repo --skill design-system-forge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-forge
Source: https://github.com/ricardohg1998-create/Plantilla-repo/tree/main/.agent/skills/design-system-forge
Command: npx skills add https://github.com/ricardohg1998-create/Plantilla-repo --skill design-system-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams establish and maintain a consistent, authorial UI by defining tokens, base UI components, and safe overrides for kits.

Core Features & Use Cases

  • Define and manage tokens (colors, typography, spacing) to ensure design consistency.
  • Build base UI components that consume tokens and support scalable kit overrides.
  • Apply governance to design decisions across 3rd-party or internal UI surfaces.

Quick Start

  • Define core tokens (colors, typography, spacing) and base UI components.
  • Create docs/design_concept.md and, if applicable, docs/ui_audit.md for kit overrides.
  • Apply across multiple screens to demonstrate consistency and governance.

Frequently Asked Questions about design-system-forge

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

FAQPage Schema
How do I establish a governed design system across multiple products?

To establish a governed design system across multiple products, you define core tokens, build base UI components, and apply governance artifacts to ensure consistency across cross-team UI initiatives.

What is token management for UI components and how does it work?

Token management for UI components involves defining and managing colors, typography, and spacing. These tokens are consumed by base UI components to ensure strict design consistency and scalable kit overrides.

How do I apply kit overrides safely without breaking design consistency?

You apply safe kit overrides by creating a UI audit document and defining base UI components that consume core tokens. This ensures third-party or internal UI surfaces maintain governance and consistency.

Do I need to create documentation files to manage design tokens?

Yes, you need to create documentation files like design_concept.md and ui_audit.md. These governance artifacts provide automated documentation for token definitions and kit override workflows.

What's the best way to manage cross-team governance for a UI component library?

The best way to manage cross-team governance for a UI component library is to enforce token definitions and base UI components, applying these rules across multiple screens to demonstrate consistency.

Can I use this approach for new UI initiatives and existing 3rd-party surfaces?

Yes, this approach applies to new UI initiatives and existing 3rd-party surfaces. It enforces token definitions and governance artifacts across internal and external UI components to maintain an authorial design.