For first builds & beyond

Build the site before you open the builder.

Most AI builds go sideways because the prep is thin, not because the tool is weak. This kit gives you the tool stack, a folder system, and six fill-in templates — so every project starts clear, consistent, and copy-ready.

01

Prep (30–60 min)

Fill the PRD, content, and design templates first. This is the brief you paste into any AI tool.

02

Build in stages

Idea → design → code → host. Use one tool per stage instead of asking one tool to do everything.

03

Launch with a checklist

Test on a real phone, check accessibility, connect the domain, and turn on analytics before you share the link.

Part 1 — The stack

What you’ll actually use, by stage

You don’t need all of these. Pick one per row to start — the “Start here” pick is the lowest-friction option for a first project.

💬
STAGE 1

Idea & Chat

Think, draft, and write the brief. Where the PRD and copy are born.

Claude / ChatGPTBrainstorm, PRDs, copy, user stories, debugging help
PerplexityResearch competitors, prices, and facts with sources
Notion / Google DocsWhere the brief lives and gets shared
Start here: One chat tool + one doc. Don’t split the brief across five apps.
🎨
STAGE 2

Design

Decide how it looks before code decides for you.

FigmaWireframes, mockups, design kits, handoff
v0 / StitchAI-generated UI drafts from a prompt — great for a first direction
CanvaLogos, social graphics, simple brand assets
Start here: Fill the Design Kit template first, then mock 1–2 key screens only.
⚡
STAGE 3

Code Builder

Turns the brief + design into a working site or app.

Lovable / BoltPrompt-to-app builders — fastest path to a live MVP
CursorAI code editor when you want control over the code
ReplitBuild, run, and host small apps in the browser
Start here: Paste your PRD as the first prompt. Build one flow at a time, not the whole app at once.
🚀
STAGE 4

Hosting & Backend

Puts it on the internet, with data, logins, and payments if needed.

Cloudflare Pages / WorkersHosting + deploys for websites and web apps — Pages for the site, Workers when you need backend logic. Netlify is a fine alternative.
Supabase / FirebaseDatabase, auth, and file storage without building a server
StripePayments, checkout, and subscriptions
Start here: Static site? Cloudflare Pages alone is enough — connect your Git repo and it deploys on every push. Add Workers / a backend only when you need logins or saved data.
🖼️
STAGE 5

Images & Content

Real photos, icons, and words — the part visitors actually see.

Unsplash / PexelsFree, license-clear photos and video
Lucide / HeroiconsConsistent icon sets — pick one and stick to it
TinyPNG / SquooshCompress images so pages load fast
Start here: Log every image in the Asset template — source + license + alt text — as you pick it.
A simple rule: If a build feels messy, the fix is almost never a different builder — it’s a clearer PRD, real copy instead of lorem ipsum, and one design direction. Come back to the templates below first.
Part 2 — Stay organized

One folder per project, same shape every time

Create this once as an empty “_TEMPLATE” folder in Google Drive or on your computer, then duplicate it for every new project and rename it.

my-project/
├── 00-brief/
│   ├── prd.md           # Tmpl 1
│   └── user-stories.md  # Tmpl 5
├── 01-content/
│   ├── content-plan.md  # Tmpl 2
│   └── copy-final.docx
├── 02-design/
│   ├── design-kit.md    # Tmpl 3
│   ├── logo/
│   └── inspiration/
├── 03-assets/
│   ├── asset-log.md     # Tmpl 4
│   ├── images/
│   ├── images-original/
│   └── icons/
├── 04-build/
│   ├── prompts.md
│   └── notes.md
└── 05-launch/
    ├── launch-checklist.md # T6
    └── analytics.md
Number the folders

00- to 05- keeps them in workflow order in any file system — brief first, launch last.

Keep originals separate

Full-res photos live in images-original/. Only compressed, web-sized copies go in images/ and into the build.

Save your prompts

04-build/prompts.md is gold. When a prompt works, save it verbatim — you’ll reuse it on the next project.

Name files like a stranger will read them

hero-living-room-1600w.jpg beats IMG_2041.jpg. Include what it is + width in the name.

One source of truth

If copy lives in the Content Plan, don’t also edit a second copy in a chat thread. Link, don’t duplicate.

Part 3 — The templates

Six templates, pre-filled with a sample project

Sample project throughout: “Little House — a direct-booking site for a short-term rental.” Edit any field to make it yours, then copy the whole template as clean Markdown — ready to paste into a doc or straight into an AI builder as your first prompt.

1 — Product Requirements Doc (PRD)

The one-page brief every tool and collaborator works from. If it’s not in here, it’s not in the build.

How to use it: Keep it to one page. Write the problem before the features — AI builders produce much better first drafts when they know why.

Name + what it is, in one sentence a stranger would understand.

2 — Content Plan

Write the real words before you build. AI builders lay out pages far better with final copy than with placeholders.

How to use it: One row per page/screen. Draft headlines first — if the headlines don’t make sense as a list, the site structure doesn’t either.

3 — Design Kit

The visual rules in one place, so every page — and every AI generation — looks like the same product. Tap a swatch to copy its hex.

How to use it: Limit yourself: 1 primary color, 1 accent, 2 fonts max, one button style. Constraints are what make a design look intentional.
Primary — Pine#2F4A3C
Accent — Cedar#C96A2B
Background — Warm paper#FFFBF3
Text — Ink#1C2321
Border / muted surface#E9E2D0
Error / destructive only#B42318

4 — Image & Asset Selection

Every image logged with where it came from, whether you may use it, and what it says for screen readers. Future-you will thank present-you.

How to use it: Add a row the moment you pick an image — not at the end. No source + no license = don’t ship it.

5 — User Stories & Flows

What people are trying to do, step by step — including what happens when it goes wrong. This is the template builders follow most literally, so be concrete.

Format: “As a [person], I want [action], so that [outcome].” If you can’t finish the “so that,” the feature probably isn’t needed yet.
Land on Home→Check availability→Pick dates→Send request→Confirmation message→Email within 24h

6 — Launch Checklist

Work top to bottom on launch day. Check items off here while you test, then copy the list into 05-launch/ for the project record.

0 of 24 checked in this session

Testing Does it work?

Mobile Most visitors are on phones

Accessibility Usable by everyone

Analytics & SEO Know if it’s working

Domain & Hosting The plumbing

Legal & Trust The unglamorous essentials

Copied