Taste is trained

Here is a small receipt card with six details switched on. Switch them off one at a time: each one alone is almost invisible. Then press All off, and All on again:

Nobody using this card would say "lovely tabular figures". They would say "this feels nice", or nothing at all, and keep using it. That is the whole idea of this module.

Unseen details compound

Paul Graham made the point first and Emil Kowalski sharpened it for interfaces: the details people consciously notice are mostly noise; the ones they don't notice are what earn their trust.

Each invisible detail does one of two things. It removes a tiny bit of friction (the amounts line up, so you compare them without effort), or it signals that someone cared (the button answers your press). People cannot point at either. They just feel the product is considered.

Twenty of these and a product stops feeling generated. That is why the skill exists: to write the unseen details down so an agent applies them every time.

Beauty is leverage

Most software does the same job as its competitors. There are dozens of to-do apps, chat apps and CRMs with the same features. When the feature list is a tie, people choose on feel, and feel is made of exactly these details.

Emil's framing is that polish is not a cost; it is leverage. Features plateau, competitors copy them in a sprint, but the last few percent of polish is slow and hard to copy. So "polish is not a priority right now" usually has it backwards: once the features are there, polish is what sets you apart.

Two limits keep this honest:

1. Correct first

   A broken product with lovely animations is still broken, and looks worse for it. Polish multiplies the trust that working software earns; it never replaces it.

2. Invisible, not theatrical

   The best polish is the kind nobody sees. Confetti on every click is not polish; a button that responds in 160ms is.

Taste is trained, not born

So who decides which details matter? Someone with taste, and taste is not a gift. It is a trained instinct, built the way any instinct is: by looking at a lot of good work, closely, for a long time.

The people whose work feels obviously right (Emil Kowalski, Benji Taylor, the Vercel design team) share one habit. They collect references: screenshots, screen recordings, products opened just to feel how a menu moves. That collection is their training set.

1. Keep a reference library

   When an interaction stops you, save it: a screenshot, a recording, a link. Rewatch them when you are stuck.

2. Use constraints

   Two fonts, three colors, one accent. Fewer choices force real decisions; unlimited choice produces average work.

3. Imitate before you invent

   Your first hundred buttons should look like buttons. A button that copies a well-made one is more tasteful than one that "innovates" with a gradient and an odd shape.

4. Expect the first version to be ugly

   Taste compounds with care. Version three is where things start to feel inevitable.

What this means with an agent

An agent has seen everything and collected nothing. It reproduces the average of all the buttons it has read, which is why its first try looks like everyone else's. Your reference library is what pulls it away from the average.

Here are three references for this settings page: [links or screenshots]. Before building, tell me in one line each what these three have in common (spacing, type, how they handle buttons). Then build the page to match those qualities, not the average settings page.

And when a screen is "done", spend the last pass on the unseen:

This screen works. Now find the details nobody would notice but everyone would feel: numbers that should use tabular figures, buttons without press feedback, pure black text, a single heavy shadow, uppercase labels without tracking. List them as a Before / After / Why table, then apply them.