design-philosophy

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill design-philosophy-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-philosophy
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/.github/skills/design-philosophy
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill design-philosophy-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI feedback often stalls on raw pixel values and personal taste, producing one-off fixes that drift out of sync. This Skill gives designers, engineers, and AI agents a shared design vocabulary so any visual surface can be evaluated against named values, principles, and concrete mechanics instead of ad-hoc opinions. ## 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 breaks, and the move that fixes it. - Concrete design moves: Reference elevation tiers (4/6/8px corner radii), the spacing ramp, type roles with two weights, 16/12px icon sizes, one-stroke borders, theme tokens, and reveal-on-intent behaviors. - Feedback phrasebook: Convert pixel-level complaints ("make this 14px") into principled statements ("this should use the label1 type role") so fixes land everywhere, not just in one spot. - 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 borders only on hover. ## Quick Start Review this dialog screenshot using the design philosophy and tell me which principles it breaks and what 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 on VS Code surfaces?▼

Lead with the feeling (Calm, Focused, Consistent, or Delightful), name the surface, identify the principle it breaks, then propose the move that fixes it. Mention pixel values only last, after the rule is named.

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

Radius is chosen by elevation tier, not taste: 4px for controls, 6px for inner containers, and 8px for floating overlays like menus and dialogs. Pick the tier by the surface's role in the stack.

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 variant; 14px is always a bug.

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

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 treated as a bug by construction.

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; decoration without purpose reads as noise.