Design System Reasoning

WHEN: Choosing UI direction, selecting a visual language, defining design tokens, filtering anti-patterns, or turning a vague product brief into a design-system-ready implementation plan.

When to Use This Skill

• Turning a product description into a usable UI direction
• Deciding which page archetype fits a product or feature
• Choosing a restrained visual language before coding begins
• Defining token guidance for color, typography, spacing, and motion
• Documenting anti-patterns for regulated, trust-sensitive, or data-heavy products
• Translating the same design intent across Tailwind, React, Vue, SwiftUI, Flutter, or plain HTML/CSS
• Reviewing whether a proposed UI direction matches audience expectations

Quick Reference