Menu
Apply restrained design taste to a UI. Use when the user wants the interface to feel tasteful, elegant, minimal, or "not overdesigned" — favors simplicity, whitespace, a tight palette, subtle motion, and removing decoration that doesn't earn its place.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diverge then converge on ideas before building. Use when the user wants options, concepts, directions, or "ideas for X" — generates multiple distinct approaches, pressure-tests them against goals/constraints, then recommends one with rationale. Pairs well with ui-ux-pro-max and goal.
Verify code against current, real library documentation before using an API. Use when working with a specific library/framework version and you must not guess APIs. Encourages checking official docs/types for the installed version. NOTE - the real Context7 is an MCP server; see setup notes below to enable live doc lookup.
Translate a design intent into clean, idiomatic frontend code. Use when building or refactoring UI components — enforces composition, design tokens, responsive layout, accessibility, and matching the surrounding codebase's conventions. For React/Vue/Tailwind/CSS work.
Clarify and pursue a goal end-to-end. Use when the user states an outcome they want achieved ("make my portfolio showcase me as X", "get this shippable"). Restates the goal, defines success criteria, plans steps, executes, and verifies the goal was actually met.
A rigorous correctness-and-detail finishing pass. Use when the user wants work to be "impeccable", flawless, production-grade, or polished to a high standard — verifies builds/lints/tests pass, hunts edge cases, checks accessibility and consistency, and refuses to claim done without proof.
Senior UI/UX craft pass for web frontends. Use when the user asks to upgrade, polish, redesign, or "make it premium/pro" — applies design-token systems, visual hierarchy, spacing rhythm, accessible color/contrast, motion restraint, and responsive layout. Best for React/Tailwind/CSS projects.
| name | taste |
| description | Apply restrained design taste to a UI. Use when the user wants the interface to feel tasteful, elegant, minimal, or "not overdesigned" — favors simplicity, whitespace, a tight palette, subtle motion, and removing decoration that doesn't earn its place. |
Good taste is mostly subtraction. This pass makes a UI feel calm, confident, and intentional.
Invoke when the user wants the design to feel tasteful, elegant, refined, or less cluttered.
Remove before you add. If an element doesn't serve the user, cut it. Borders, shadows, gradients, and icons must each earn their place.
One accent, lots of neutral. A single confident brand color against a well-considered neutral scale beats a rainbow. Use accent sparingly for emphasis and interaction.
Whitespace is a feature. Let content breathe. Crowded ≠ rich.
Type does the heavy lifting. A clear type scale and good line-height create hierarchy without decoration. Limit to 1–2 families.
Subtle motion. Prefer 150–250ms eases and small movements. If an animation calls attention to itself, it's probably too much.
Consistency reads as quality. Same radius, same spacing units, same button shapes everywhere. Inconsistency looks like a bug.
Restraint with effects. Glass, glow, blur, parallax — at most one "wow" moment per view, supporting the content, never competing with it.
Note what you removed/simplified and why — taste is visible in the cuts.
