agentleFS
Wang-CankunWang-Cankun/cankun-skills/skills/taste/SKILL.md

taste

Skill2 starsChanged 31 days agoMITView on GitHub

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.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use council, ui-ux-pro-max and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    council

    Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Simple: Every element earns its place by serving the need from step 2, or by a stated contribution such as pleasure, expression or identity.

    line 53
  2. Distinctive:

    When you lack the knowledge to judge (the essay's point that good work clusters where capable people work on related problems), find the …

    line 78

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 the problem would meet that need more directly. Done when the sentence names person, moment and need, each sourced or marked as assumed, and the objective is told apart from its proxies.
  3. Find the organising idea (added technique). Name the idea the work hangs on (a subway map, a gate the user stands at, one table threading through every output) and make the hierarchy show it: the central task or relationship is recognisable at first look, by position, weight or size as the medium allows. Done when the idea can be stated in a phrase and the hierarchy shows the central task.
  4. Revise (the essay: good work is usually redesign). Make a substantive revision aimed at the weaknesses from step 1, and compare it with the original. Work in a form that makes mistakes cheap to see and fix (a sketch, a draft, a throwaway version) before committing to the expensive one. The central idea may survive; the revision fixes what was found. When reviewing rather than making, propose the revision concretely. Done when the revision exists or is proposed, and the comparison states which is better and why.
  5. Test. Apply the tests below that bear on this work, each with evidence. Done when every applicable test has evidence of meeting it, a named and accepted cost, or the mark unresolved with the evidence that would settle it; each test you set aside has the reason it does not apply.

Tests

  • Simple. Every element earns its place by serving the need from step 2, or by a stated contribution such as pleasure, expression or identity. Decoration that disguises a weak structure goes; decoration that adds to a sound one may stay.
  • Timeless. It avoids leaning on a passing style. If you can already imagine a better version, structure or reasoning, it is not done.
  • Right problem. It meets the objective from step 2, not its proxy, and fits how the thing is used (controls laid out like what they control).
  • Suggestive. It hands the person elements to build with and room to complete it.
  • Light touch (optional). It is confident enough to carry a little humour where the subject allows.
  • Hard-won. Difficulty inherent in the task was met; friction that serves nothing was removed. Precision is highest where the person notices small errors most.
  • Looks easy. The result looks unforced: few elements, each exactly right. That ease usually comes from practice and many revisions; judge the result, not how hard it was to make.
  • Symmetry with care. Repetition and recursion simplify it; they stand in for no decision.
  • Like nature. Where a natural form or process solves a similar problem, the borrowing is explained in terms of the constraints that make it fit here.
  • Copies well. A human-made precedent (a map, a ledger, a known interface) is borrowed knowingly and from the source: the precedent is named, with why its answer applies. Unknowing imitation, often of something that was itself an imitation, is a common source of generic work.
  • Strange, honestly. Whatever is surprising came from pursuing the problem, and stays when it serves the answer rather than being smoothed away. Strangeness is neither a target nor a defect.
  • Daring. Where accepted practice and the facts of this case part, it follows the case.

When you lack the knowledge to judge (the essay's point that good work clusters where capable people work on related problems), find the field's strong work or a practitioner's criticism and judge against that.

Reporting a review

Open with the problem sentence and the organising idea. Then each finding as: the element (a control, a node or relationship, a passage), the test it fails with its evidence, and the change. Close with the proposed revision from step 4.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.