design-system-definition

Define design tokens, typography, spacing, and component behavior rules.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill design-system-definition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-definition
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/design-system-definition
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill design-system-definition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establish a single, coherent visual language by defining tokens, typography, spacing, and component behavior rules to prevent UI drift and rework.

Core Features & Use Cases

  • Visual_direction specification to guide UI design
  • Design_tokens_guidance covering tokens, typography, and spacing
  • Typography_rules, spacing_rules, and component_behavior_rules
  • Accessibility_notes to ensure inclusive design
  • Use Case: apply to a SaaS dashboard redesign to align brand and improve developer handoff

Quick Start

Provide a brand direction or existing style baseline and a wireframe plan to generate an implementation-ready visual system.

Frequently Asked Questions about design-system-definition

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

FAQPage Schema
How do I define design tokens to ensure UI consistency across a product redesign?

Design tokens standardize UI elements by defining reusable variables for typography, spacing, and component behaviors. This ensures UI consistency across new user-facing surfaces by translating a cohesive visual language into developer-ready implementation rules.

What is included in a complete design system specification for developer handoff?

A complete design system specification includes visual direction, design token guidance, typography rules, spacing rules, component behavior rules, and accessibility notes. These outputs prevent UI drift by establishing a single, coherent visual language for developer implementation.

How do I build accessibility rules into my UI component behaviors and spacing?

Build accessibility rules into component behaviors by generating dedicated accessibility notes alongside spacing and typography rules. This ensures inclusive design is enforced systematically across all user-facing surfaces rather than handled as an afterthought.

Can I use this to align a SaaS dashboard redesign with existing brand guidelines?

Yes, you can apply this to a SaaS dashboard redesign by providing an existing brand style baseline and wireframe plan. It generates an implementation-ready visual system that aligns the UI with your brand while improving developer handoff.

What is the best way to prevent UI drift and rework when scaling a visual language?

The best way to prevent UI drift is to establish a single, coherent visual language using strict token, typography, and spacing rules. Defining these parameters systematically stops visual fragmentation and reduces development rework across new surfaces.

Why does my UI design system need component behavior rules and not just visual tokens?

Component behavior rules are needed alongside visual tokens to define how UI elements interact and respond, ensuring functional consistency. While tokens manage visual properties like typography and spacing, behavior rules dictate interaction patterns for cohesive user experiences.