agentleFS
obakeng-developsobakeng-develops/taste/skills/taste/SKILL.md

taste

Skill0 starsChanged 5 months agoMITView on GitHub

Apply cultivated taste to interfaces and to prose. Covers UI, layout, typography, product flows, visual polish, and writing — UI copy, docs, messaging, names. Use when designing or critiquing interfaces, writing front-end/CSS, building artifacts, drafting or editing any user-facing text, or when the user mentions taste, polish, jank, design, typography, layout, writing, copy, clarity, or "make it feel good". On invocation, read the taste library for the user's saved examples (see below).

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

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 6

    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:

    Every element should show how it works.

    line 30
  2. Distinctive:

    Lead with the user's real question: Put the answer in the biggest type.

    line 40
  3. Distinctive:

    Warm and human: Write like one person talking to another, in your own voice.

    line 50
  4. Distinctive:

    Read it aloud: If it stumbles, fix the rhythm.

    line 52
  5. Distinctive:

    Prototype throwaway: before the design or draft hardens — early is cheap.

    line 57
  6. Distinctive:

    Name the why: when something works or fails.

    line 58

“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

Taste is noticing what makes something feel great, then reproducing it on purpose. You learn it by exposure, not birth. It works the same in two domains: interfaces and prose. Fix the floor before you reach for meaning.

Read the taste library first: ~/.claude/taste/references.md. It holds the user's examples and the why behind each. Let it set the specifics. If that file does not exist yet, seed it once by copying references.template.md from this skill's directory to ~/.claude/taste/references.md (create the ~/.claude/taste/ directory if needed), then read it.

Interfaces

Layer 1 — Kill the jank

Most bad design is just sloppiness no one cleaned up.

  • Align everything. Share edges; use a grid. Scattered reads as careless.
  • One typeface, vary the weight. Many fonts read amateur.
  • Body text is most of typography. Order that matters: body look → size → line spacing → line length → font. Web body 15–25px, line-height 1.3–1.45 unitless, 45–90 characters a line. Font choice comes last.
  • Audit for drift. Taste erodes by small inconsistencies. Clean them up.

Layer 2 — Affordances

Every element should show how it works. Software affordances are conventions (radio picks one, checkbox picks many, the default button is the safe path). Honor them, or break them on purpose — never by accident.

Layer 3 — Story and emotion

Design is narrative, and the user finishes it (Lupton).

  • Flows have an arc: setup, tension, resolution. Onboarding, empty states, errors, and success are beats, not screens.
  • Work all three registers — gut, use, memory (Norman: visceral, behavioral, reflective).
  • Show, don't tell. Restraint and the right gaps let people infer meaning.
  • Lead with the user's real question. Put the answer in the biggest type.

Prose (Zinsser, On Writing Well)

Clear writing is clear thinking. Same taste, different medium.

  • Cut clutter. Strip every sentence to its cleanest parts. Drop the words that earn nothing — "in order to", "the fact that", qualifiers like "very", "quite", "sort of", adverbs that just repeat the verb.
  • Plain words. Short, common ones over fancy ones. No jargon.
  • Active voice, strong verbs. The subject acts. Verbs carry the sentence.
  • One thought per sentence. Let the reader keep up.
  • Warm and human. Write like one person talking to another, in your own voice.
  • Rewriting is the work. First drafts are clutter. The polish is the cutting.
  • Read it aloud. If it stumbles, fix the rhythm.

Practice

  1. Subtract first. Removing the second font, the flourish, the extra step, the spare word is usually the higher-taste move. Same instinct in both domains.
  2. Prototype throwaway before the design or draft hardens — early is cheap.
  3. Name the why when something works or fails. That sentence is the skill.

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.