Skip to content
SkillModel-led2,113 tokens in use

learn-taste

Collects the design corrections made in a session and turns each into a rule with its reason in DESIGN.md, a project skill or a lint check.

58,388 stars on the repository MIT Licenseemilkowalski/skills · skills/learn-taste
npx skills@latest add emilkowalski/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing learn-taste costs

30tokens idle
2,113tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples15/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance40
  • Community52
  • Maturity28
  • Momentum40

Learn Taste runs at the end of a session. It reads the conversation, including edits you made yourself, filters real corrections from noise, generalizes each into a rule, finds the reason behind it and decides where the rule should live. It proposes the rules, stops, and writes only what you approve, so the next agent repeats no mistake. It is set to run only when invoked.

What You Get

  • A list of proposed rules, each with its reason
  • Questions for rules where the reason is unknown
  • A conflicts list when a rule clashes with an existing one
  • Suggested lint rules or checks for violations that code can detect

Common Use Cases

  • Ending a design session by recording the corrections
  • Building a DESIGN.md that agents follow
  • Turning a repeated visual mistake into a lint rule

What Makes It Unique

Every rule traces to something you said, edited or confirmed, and a reason is never invented: an inferred reason is marked and confirmed first. It prefers a check over a sentence, since a lint rule runs every time and a line in a long file can be skipped.

Under The Hood

A single SKILL.md with no scripts. The model reads the current conversation and, if you name earlier sessions, their Claude Code transcripts under the projects folder in your home directory. It proposes rules, waits, and then writes to DESIGN.md or the chosen surface once you approve.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers