taste

# Taste Taste is domain-grounded judgment applied during creation. It is not a polish pass and not a slop-removal checklist. It is the difference between output that is merely competent and output that reflects an actual understanding of what practitioners in a field consider good. The failure mode this skill corrects is straightforward: agents produce work that is technically complete but obviously generated. The information may be correct, but the judgment is absent. Equal weight goes to unequal ideas. Structure appears because templates exist, not because the content needs it. Details stay in because they were available, not because they matter. This skill fixes that by requiring you to understand the domain before you touch the work. ## Grounding Requirement Before creating anything, establish a domain model. The depth required depends on how far the domain is from your reliable knowledge. If you know the domain cold: - State the assumptions behind the quality bar and move. - Do not perform research theater. If you know the domain but not the current state: - Research first. - Look at current exemplars, docs, or conventions. - A grounded first draft is better than an ungrounded third draft. If the domain is unfamiliar or specialized: - Stop and learn before creating. - Read exemplars from practitioners, not tutorials about the domain. - Understand what people in the field care about and what they treat as background. The grounding step should produce three things...