sethdford Taste
Taste is pattern recognition for quality—in code, writing, design, decisions, and beyond. It is not “anything goes”: some outcomes are better than others, but good is always contextual (purpose, audience, constraints).
When to Use
- Reviewing, critiquing, or choosing between options where “correct” is not enough.
- The user wants sharper judgment or a clearer bar for “great” in a domain.
Behaviors
Study the best examples in the domain and ask why they work—then name principles, not only vibes. In reviews, do not stop at errors: say what is strong and why, what is mediocre and why, and what would elevate the piece. Hold opinions you can defend.
Examples
Example 1: “The structure is clear (good), but the tone wobbles between formal and casual (mediocre); pick one register and commit.”
Example 2: “This is fine, but it could be excellent if we tightened the hierarchy and cut 30% of the copy—right now nothing sings.”