design-philosophy

Applies a Values-Principles-Moves vocabulary to review and fix VS Code UI design decisions.

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill design-philosophy-kevinhuangislearning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-philosophy
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/.github/skills/design-philosophy
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill design-philosophy-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI feedback often stalls at vague pixel-level complaints like "make this 6px" or "this feels off," which fix one spot and drift back out of sync. This Skill provides a shared design vocabulary—Values, Principles, and Moves—so designers, engineers, and agents can name the rule a surface breaks and land the fix everywhere it applies. ## Core Features & Use Cases - Three-layer reasoning framework: Translate a "this feels off" observation into a named value (Calm, Focused, Consistent, Delightful), the principle it breaks, and the concrete move that restores it. - Concrete design tokens and ramps: Reference elevation tiers (Control 4px / Inner 6px / Outer 8px radii), the spacing ramp, type roles with two weights, 16px/12px icon sizes, one-stroke borders, and theme color tokens. - Feedback phrasebook: Convert pixel-level complaints into principled statements (e.g., "this overlay is rounded at the wrong elevation tier") for design reviews and code reviews. - Use Case: When reviewing a busy settings panel, identify that it breaks "Quiet at rest" and "One thing leads," then demote secondary text to a quieter type role and reveal chrome only on hover. ## Quick Start Ask the assistant to review a UI surface or screenshot using the VS Code design philosophy and name which value, principle, and move apply.

Frequently Asked Questions about design-philosophy

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

FAQPage Schema
How do I give actionable UI design feedback in code review?▼

Lead with the feeling (which value is missing: Calm, Focused, Consistent, or Delightful), name the surface, state the principle it breaks, then suggest the move that fixes it. Only mention pixel numbers last, since naming the rule fixes the issue everywhere it occurs.

What corner radius should I use for a VS Code UI element?▼

Radius is chosen by elevation tier, not taste: Control tier is 4px for interactive elements, Inner is 6px for containers inside a surface, and Outer is 8px for floating overlays like menus and dialogs. Pills use the fully round circle token.

What icon sizes does the VS Code design system allow?▼

Codicons are only 16px (base) or 12px (compact); 14px is always a bug. Use base for standalone primary actions and compact for dense rows or inline glyphs, swapping to the *Compact glyph variant at 12px for optical tuning.

Can I use hardcoded hex colors or font-weight 500 in VS Code UI?▼

No. Every color must be a --vscode-* theme token so the UI tracks themes and high-contrast modes, and type has only two weights: regular (400) and semiBold (600). A hardcoded hex or weight 500 is off the ramp by definition.

When is animation appropriate in a VS Code interface?▼

Motion must do a job: guide the eye, confirm an action, or orient the user. Keep it subtle, short, and interruptible, honor prefers-reduced-motion, and cut any transition that is purely decorative.