References over theory

You don’t need design school. You need a camera roll of good taste.

You don't need design school. You need a camera roll of things that look good, and the sentence “make mine feel like this.” That's the entire theory section of this chapter.

Agents are excellent executors of taste and mediocre inventors of it. Prompt with no visual direction and you'll get the same competent-but-generic layout everyone gets. Prompt with a screenshot of a site you love and the difference is night and day. So the real design skill is collecting: screenshots, links, tiny details you noticed, gathered before you need them.

Where to hunt

• –Mobbin holds thousands of real app screens, searchable by pattern. The best single source for “how do good apps do this screen?”
• –Awwwards and Dribbble are the ambitious end of web design. Steal moods here, not layouts.
• –CodePen and 60fps.design are for interactive details and motion. When you find one, link it to your agent directly.

One prompt, three personalities

Something nobody tells beginners: models have taste. Hand the identical landing-page prompt to Claude, GPT, and Gemini and you get three different aesthetics, like briefing three designers. So audition: same prompt, two or three models, keep the one closest to your head. (In Cursor this is a dropdown; with agents, /model.) The community's loose consensus (Gemini polished out of the box, Claude best in conversation, GPT boldest) matters less than the auditioning habit itself.

Here's a screenshot of a site whose feel I love [attach]. Rebuild my landing page hero in this spirit, not a copy: keep my content and colors, borrow the spacing, type scale, and confidence.

AI Clubhouse · Vibe Coding Guide