- AI MVP Weekly
- Posts
- My workflow for building beautiful AI websites
My workflow for building beautiful AI websites
6 tools that made AI design actually work. Here's the workflow.

Hey builders,
Most AI websites still look mid.
Not because AI can't design.
Because people skip the basics.
Here's my actual workflow for building beautiful websites with Cursor and Claude.
1/ Decide your colors before you write a single prompt
Most people jump straight into Claude and wonder why everything looks inconsistent.
I spend 5 minutes on Coolors first. Pick a palette. Export it.
This one decision saves hours of "make it look better" prompts later.
2/ Design before you build
Asking Claude to design and code at the same time is a mess.
I use Google Stitch with Gemini 3 Pro to get the UI right first. Clean layouts. Minimal. Balanced.
New update: you can generate a working prototype directly from the design. Then export and bring it into Claude.
Way cleaner than prompting blind.
3/ Stop describing designs from scratch
AI is good. But showing is faster than telling.
I grab screenshots from galleries like Superhero for hero sections, navbars, footers.
Drop the screenshot into Stitch. Let it replicate the vibe for my project.
10x faster than typing "make it modern and clean" over and over.
4/ ShadCN presets changed how I style components
ShadCN now lets you create style presets before importing anything.
Play with the components. Adjust until it fits your vibe. Hit create project.
One install command and your entire component library is styled consistently.
No more fighting with random button colors.
I did a short video on shadcn/create. Check it out here.
5/ Drawbridge for the small stuff Claude keeps missing
Sometimes Claude just won't fix a tiny UI bug no matter how you explain it.
Drawbridge has Claude Code integration now. You select the section visually, point at the issue, done.
No more "move the button 2px to the left" back and forth.
6/ Background agents are underrated
Claude now lets sub-agents run in the background.
I use Puppeteer MCP for browser testing. Takes time. So I run it in the background and give Claude another task.
Multiple agents. Parallel work. Better use of tokens and time.
Quick recap
Colors first (Coolors)
Design in Stitch before coding
Screenshots > descriptions
ShadCN presets for consistency
Drawbridge for visual fixes
Background agents for speed
Stop shipping ugly UI. The tools exist. Use them.
Keep building,
~ Prajwal
PS: I’m rebuilding the entire Build Module for 2026 using the latest AI stack I actually use today. This will drop around Jan–Feb and will be the only “build with AI” system you’ll need to ship SaaS in 2026 and beyond. Lock in now before the price goes up.