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_exploration.md
View on GitHub# Taste Exploration
Use this before choosing references.
The goal is to discover the right taste direction for this product, not to decorate the UI.
## Provenance
This module is a synthesized operating guide, not a verbatim extraction from one source.
It combines:
- Claude-style design collaboration: explore context, ask useful questions, show taste judgment early, avoid filler.
- Reference-system thinking: convert reusable style traits into concrete choices without copying brands.
- Agent-executable design brief thinking: turn taste into explicit rules an implementation agent can follow.
- Variation-first thinking: compare meaningful directions when taste is uncertain.
- UI critique principles: judge hierarchy, clarity, affordance, visual weight, consistency, and user-task success.
## Taste Questions
Answer these from project context before opening detailed references:
- What is the product really doing for the user?
- What should the surface make the user feel: trust, speed, calm, control, delight, precision, warmth, authority, focus?
- What is already working visually and should not be erased?
- What is weak, generic, noisy, unclear, cramped, or visually dishonest?
- What should become more visible: task entry, data, comparison, status, identity, next action?
- What would make this UI worse even if it looked more designed?
## Direction Axes
Explore along meaningful axes:
- calm vs energetic
- editorial vs operational
- light workspace vs dark cockpit
- sparse search tool vs dense analysis surface
- institutional trust vs consumer warmth
- data-first vs narrative-first
- existing identity preserved vs visual reset
- single-task clarity vs multi-module command center
## Required Taste Readout
Before reference selection, summarize:
- product identity in one sentence
- strongest existing visual cue
- weakest current UI problem
- recommended taste direction
- one direction to avoid
- why this recommendation makes the UI more useful, not just more styled
This readout is the second investment gate.
Ask the user which taste direction is worth investing in, not whether the process should continue and not which reference brand sounds good.
## Taste First, Reference Second
Do not choose a reference because the product category sounds adjacent.
For example:
- EV does not automatically mean dark automotive cockpit.
- AI does not automatically mean gradients or black glass.
- Data dashboard does not automatically mean Linear.
- Search/query tools often need restraint more than visual novelty.
If the taste readout suggests the existing product already has the right emotional tone, use references lightly.
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 |