design-philosophy

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

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill design-philosophy-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-philosophy
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/design-philosophy
Command: npx skills add https://github.com/Niiihuel/openide --skill design-philosophy-niiihuel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI feedback often stalls at pixel-level nitpicks like "make this 6px," which fixes one spot while the underlying design rule stays broken everywhere else. 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 consistently across the codebase. ## Core Features & Use Cases - Three-layer reasoning framework: Translate a vague "this feels off" observation into a named value (Calm, Focused, Consistent, Delightful), the principle it violates, and the concrete move that restores it. - Concrete design tokens and ramps: Reference elevation tiers (Control 4px, Inner 6px, Outer 8px), the spacing ramp, type roles with two weights, 16px/12px icon sizes, one-stroke borders, and theme-based color tokens. - Feedback phrasebook: Convert pixel-level complaints into principled statements, e.g. "this overlay is rounded at the control tier" instead of "border-radius should be 6." - 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 Review this dialog's styling using the design philosophy and tell me which principles it breaks and which moves would fix it.

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 VS Code?▼

Lead with the feeling (Calm, Focused, Consistent, or Delightful), name the surface, state the principle it breaks, then propose the move that fixes it. Only mention pixel numbers last, after the rule is named.

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

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

What icon sizes does VS Code support for codicons?▼

Codicons come in exactly two sizes: 16px base for standalone or primary actions, and 12px compact for dense rows and inline glyphs. At compact size, swap to the matching *Compact glyph; 14px is always a bug.

Can I use hardcoded hex colors in VS Code UI code?▼

No, every color must come from a --vscode-* theme token so the UI tracks the active theme and high-contrast modes. A hardcoded hex is a bug by construction; report it as a wrong theme token issue.

When should UI animation be added in VS Code?▼

Only when motion does a job: guiding the eye, confirming an action, or orienting the user. Keep it subtle, short, interruptible, and honor prefers-reduced-motion; decorative animation is treated as noise.