Who this is for
Designers, builders, and anyone who wants an AI assistant to design in their style instead of the average of everyone’s.
For DesignersPDF · 13 pages · Version 1.0 · September 2026
A Component Taste Library
Designers and builders make hundreds of small interface decisions. Without a written taste layer, every project starts from zero, and AI-assisted builds drift toward generic defaults. This guide builds you a personal library of real, working examples to rate, plus a written taste file your future builds can follow.
Free. No email required. The download is the complete guide, not a sample.
What is inside.
The guide runs as an interview and a build, in five parts, with the working rules in an appendix at the back.
The setup interview
What the library is for, which component categories you want, and your visual defaults, such as light or dark surfaces and any brand tokens.
The gallery
Over 100 real, working interface examples, built to be clicked and tried, not just looked at.
Keep-or-cut reviews
Small batches of verdicts, with your reasons recorded as you give them.
Your taste file
What you like and why, written as reusable rules your future builds can follow.
My Picks
Your focused collection: every example you kept, without searching the full gallery again.
The technical appendix
The detailed working rules your assistant builds and reviews by.
The core idea.
Your preferences should guide your work; they should never be presented as universal rules for what counts as good design. The taste file keeps those two layers separate on purpose: universal UX principles in one place, your personal taste in another, so a future build knows which kind of rule it is following.
That separation is what makes the library safe to reuse, and safe to share.
The start-here prompt.
Attach the PDF to a conversation with an AI assistant and paste this. The setup interview comes first.
The prompt, exactly as printed
I want to build a Component Taste Library using the attached guide. Please walk me through it in plain language. Before you build anything, interview me about what the library is for (my own work, client work, showing clients options, or a mix), which component categories I want, and my visual defaults such as light or dark surfaces and any brand tokens. Then research real component patterns, build me an interactive gallery, and interview me in small batches where I say keep or cut and why. Record my verdicts in a taste file that separates universal UX principles from my personal taste. Do not publish or share the gallery without my explicit approval.
Take the whole guide.
The complete workflow: interview, gallery, review batches, taste file, and the appendix.