Week #17: Agent Taste
Four bookmarks around the same question: how much visual taste can you package up and hand to a coding agent?
design.md
The most literal version — a proposed DESIGN.md format from Google Labs for describing a visual identity to coding agents. I like the bluntness of this: not another component framework, just a structured file that says “this is what the thing should feel like” before the agent starts spraying Tailwind around.
google-labs-code
awesome-design-md
Takes the same idea and turns it into a library shelf — a collection of DESIGN.md files reverse-shaped from known websites. The useful part is not really imitation, but calibration: giving an agent enough visual reference material that it stops treating “make it nice” as permission to invent startup gradients.
VoltAgent
ui-ux-pro-max-skill
The messier cousin of the same impulse — a skill that tries to package design intelligence for AI-assisted UI work. It has the slightly overstuffed energy these things often have, but it points at the same gap: coding agents are now good enough at implementation that the bottleneck moves upstream into taste, hierarchy, spacing, and knowing when not to add another card.
nextlevelbuilder
pretext
Sits slightly off to the side, but belongs in the same folder — an experiment from Cheng Lou around text, structure, and interface generation. Compared with the more explicit agent-design files above, this feels less like “give the model a brand guide” and more like “change the substrate the interface is made from.”
chenglou👋
No spam, no sharing to third party. Only you and me.
Member discussion