DonkeyKing01/tasteful-ui-skill / tasteful-ui
tasteful-ui
VerifiedUI design and implementation for real product surfaces with taste-first critique, reference routing, project-specific design briefs, variation comparison, and implementation verification. Use when Codex should redesign, build, polish, or critique frontend UI by reading project context, exploring taste, routing through `references/catalog.md`, synthesizing `PROJECT_DESIGN.md` or `design.md`, using investment gates to avoid wrong taste/reference/scope, implementing in the existing stack, and evaluating whether the result is actually better. Best for app screens, dashboards, landing pages, query tools, product surfaces, and design explorations; not for backend-only work or tiny cosmetic edits.
taste/taste_critic.md
View on GitHub# Taste Critic
Use this to judge proposed directions, `PROJECT_DESIGN.md`, and final screenshots.
## Scoring
Score each UI from 1 to 10 across:
- Product fit: Does the visual direction match the product's real job and audience?
- Hierarchy: Can the user see what matters first, second, and third?
- Clarity: Are labels, actions, data, and states easy to understand?
- Taste: Does it feel intentional without looking templated?
- Restraint: Did the design avoid unnecessary decoration, filler, and style cosplay?
- Density: Is the amount of information appropriate for the task?
- Craft: Are spacing, type, alignment, contrast, and component states polished?
- Responsiveness: Does the design survive mobile and narrow layouts?
## Red Flags
Treat these as serious failures:
- The redesign looks more complex but less useful.
- A reference style is visible but the product identity is weaker.
- Charts, labels, or controls overlap.
- Dark mode reduces readability without adding functional value.
- The page looks like a generic SaaS template.
- The design adds hero copy, cards, or stats that do not serve the user task.
- The strongest existing product cue was removed without reason.
- The UI passes build checks but fails visual judgment.
## Critique Questions
Ask before approving implementation:
- Is this better than the original UI?
- What exactly improved?
- What got worse?
- Would a user complete the task faster or with more confidence?
- Did the reference strengthen the product or merely recolor it?
- Which part should be simplified?
- Which part needs more craft?
## Compare Variants
When comparing variants, do not reward novelty alone.
Prefer the direction that best balances product fit, clarity, taste, and implementation realism.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |