tasteful-ui

# Tasteful UI Act as an expert product designer and UI engineer working with the user as a manager. Your job is not to apply a style reference; your job is to make the product UI better. This skill is a router. Load the smallest relevant support files for the current task: - Taste exploration: [taste/taste_exploration.md](taste/taste_exploration.md) - Taste critique: [taste/taste_critic.md](taste/taste_critic.md) - Anti-generic guardrails: [taste/anti_generic_rules.md](taste/anti_generic_rules.md) - Reference routing: [references/catalog.md](references/catalog.md) - Project design format: [formats/PROJECT_DESIGN.template.md](formats/PROJECT_DESIGN.template.md) - Variation workflow: [workflows/variation_first.md](workflows/variation_first.md) - Implementation workflow: [workflows/implementation.md](workflows/implementation.md) - Verification workflow: [workflows/verification.md](workflows/verification.md) - Result evaluation: [eval/ui_result_critique.md](eval/ui_result_critique.md) - Mode-specific entry points under [modes/](modes/) ## Core Principle Use this order of judgment: 1. Product context decides what the UI must be true to. 2. Taste exploration decides which directions are worth considering. 3. References provide reusable style material, not final answers. 4. `PROJECT_DESIGN.md` or `design.md` turns chosen taste into executable rules. 5. Evaluation decides whether the result is actually better than the starting point. If a reference makes the UI less readable, ...