| name | ui-taste-pro |
| description | High-taste UI judgment for avoiding generic AI-looking interfaces and improving product feel. Inspired by Leonxlnx/taste-skill and adapted for Codex v4.3. Use for UI beauty, frontend aesthetics, visual direction, layout taste, avoiding generic slop, and reviewing whether an interface feels polished or amateur. |
UI Taste Pro
Purpose
Improve taste, not just styling.
Use this alongside ui-polish-pro, frontend-design-pro, or figma-to-code when UI quality matters.
Taste Principles
- Start with hierarchy and intent before color.
- Make the interface feel specific to the product domain.
- Use fewer, stronger visual decisions.
- Prefer rhythm, spacing, alignment, and typography over decoration.
- Make empty, loading, and error states feel intentionally designed.
- Operational software should feel efficient, quiet, and scannable.
- Expressive pages should still show the actual product, object, or experience.
Anti-Slop Checklist
- No generic purple gradient default.
- No decorative blobs or floating orb backgrounds.
- No card-in-card layouts.
- No oversized marketing hero inside an app screen.
- No vague "modern" design without concrete hierarchy.
- No text overflow or cramped button labels.
- No inconsistent radius, icon size, shadow, or spacing scale.
- No fake depth that does not clarify grouping.
Design Review Questions
- What should the user notice first?
- Is the main action obvious but not loud?
- Can a user scan the page in five seconds?
- Do states look designed or accidental?
- Does spacing communicate grouping?
- Does the palette contain enough contrast and restraint?
- Does the UI match the product category?
Output
State visual diagnosis, strongest taste issue, concrete fix list, and verification viewports.
Boundaries
- Do not claim files, generated media, deployments, scans, account changes, or external writes unless the active tool or command output proves them.
- Do not override system, developer, user, project, or selected-skill rules.
- If another skill is more specific for the user's intent, hand off or use it as the main skill instead of duplicating its workflow.
