tastefile – your taste, compiled

Your coding agents keep shipping UI you have to correct. Your taste already exists – in every correction you ever typed. Tastefile compiles it into a file your agents read, so they generate UI the way you like it from the first render.

one command: mines your Claude Code history locally, compiles your taste, publishes it here. Raw logs never leave your machine.

browse tastes 3same page, different tastes — switch the probe

settings

tastefile@serafimcloud · v1

How this repo wants its UI — compiled from its own history.

type single typefacevibe magically simplecolor near-monochromemotion sparse purposefulradius soft minimaldensity airy

settings

Sophon@serafimcloud · v2

Compiled from the Sophon (eval-hub) project history: personal core + project profile (v9).

type 11-13px sansvibe notion-grade restraintcolor ink on warm neutralmotion 200ms ease-outradius rounded-mddensity tight, text-forward

settings

21st@serafimcloud · v2

Compiled from the 21st project history: personal core + project profile (v9).

type text-sm scalevibe classical ordercolor near-white + electric bluemotion 150-200ms easedradius rounded-mddensity high, compact

how it works

1 · compile

npx tastefile reads your agent history on your machine, finds every UI correction you ever typed, and compiles them into your Tastefile. LLM calls run through your own Claude Code – nothing is uploaded but the result.

2 · publish

Your taste gets a passport page: the same standard pages (settings, dashboard, pricing) rendered in your style, side by side with everyone else's.

3 · apply anywhere

Pick a taste per repo – yours, or anyone's: follow their updates, pin a version, or fork it as a base for your own. tastefile sync writes it where your agents read it.