ui-design-system

Generate design tokens, component documentation, and developer handoff assets.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/pohlai88/AFENDA-NEXUS --skill ui-design-system-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-design-system
Source: https://github.com/pohlai88/AFENDA-NEXUS/tree/main/.agents/skills/ui-design-system
Command: npx skills add https://github.com/pohlai88/AFENDA-NEXUS --skill ui-design-system-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams build and maintain scalable design systems by generating tokens, documenting components, and producing handoff artifacts that connect design and development.

Core Features & Use Cases

  • Design token generation: create color, typography, spacing tokens from brand inputs.
  • Component documentation: generate API-ready docs for components and usage patterns.
  • Responsive design calculations & handoff: provide breakpoints, fluid typography, and developer handoff artifacts.
  • Use Case: teams delivering multi-product platforms can reuse a single design system across products.

Quick Start

Create tokens for a brand color, document a starter component catalog, and prepare a handoff package.

Frequently Asked Questions about ui-design-system

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

FAQPage Schema
How do I generate design tokens from brand inputs for a multi-product platform?

Design token generation extracts color, typography, and spacing inputs from your brand guidelines to produce standardized tokens. This ensures UI consistency across multiple products while automating the maintenance of your scalable design system.

What is the best way to prepare developer handoff assets for component documentation?

Preparing developer handoff assets involves generating API-ready documentation for your components and their usage patterns. This process bridges the gap between design and development by providing the exact specifications needed for implementation.

Can I calculate responsive design breakpoints and fluid typography within a design system?

Responsive design calculations provide specific breakpoints and fluid typography rules for your components. This ensures your UI system adapts seamlessly across different screen sizes while maintaining visual consistency.

Does this approach work for teams building a scalable design system across multiple products?

Yes, this approach is specifically built for design teams delivering multi-product platforms. It enables you to reuse a single design system across different products, ensuring consistency and enabling fast collaboration between design and development.

What do I need to start automating component documentation and token creation?

You need your foundational brand inputs, such as color palettes and typography scales, to start generating design tokens. From there, you can document a starter component catalog and prepare a complete handoff package.

Why use design tokens instead of hardcoding values in component documentation?

Using design tokens instead of hardcoded values centralizes your styling decisions, making component documentation easier to maintain. This allows teams to update branding globally across multiple products without rewriting individual component code.