← ClaudeAtlas

tastelisted

Taste in made things. Use when improving a design, UI, diagram, document or code structure that works but is unsatisfying, when choosing between design alternatives, or when reviewing a design.
Wang-Cankun/cankun-skills · ★ 2 · Web & Frontend · score 69
Install: claude install-skill Wang-Cankun/cankun-skills
# Taste Grounded in Paul Graham's 2002 essay "Taste for Makers" (https://paulgraham.com/taste.html), which this skill paraphrases; read the original when a judgement turns on its argument. Its premise: taste is not mere preference. Makers improve, so their earlier work was worse, and the same principles of good work recur across mathematics, painting, engineering and writing, so a lesson from one field can judge another. Correctness and taste are not separate stages: noticing that something is ugly is often how a technical flaw is found. The steps are the working method; the tests are the essay's principles as questions, adapted as heuristics for judging work, not a score. Step 3 adds a technique of this skill's own (marked), built on the essay. ## Steps 1. **Diagnose.** Say what is ugly or unsatisfying, specifically: the element, and why, backed by knowledge of the field, a comparable example, or how the thing is actually used. The essay's closing point is that good work starts from this dissatisfaction, joined to enough knowledge to see a better answer. Done when each complaint names an element and its evidence. 2. **Name the problem.** State who uses the thing, at what moment, and what they need then, from the context you were given; mark any part you assumed. Separate the real objective from an attractive proxy for it (letters that look pure versus letters that are easy to tell apart), and ask whether a different or easier equivalent framing of th