Getting started — Catchup AI Prompts
The pack builds Catchup one prompt at a time. Each prompt describes one part of the site exactly — sizes, spacing, text styles, motion, content — and names the screenshots that show how it should look. This guide takes you from the download to a finished site.
What you need
Section titled “What you need”- An AI tool that writes and runs a website: a chat builder (Lovable, Bolt, v0, Replit) or a coding agent (Cursor, Claude Code, Codex, Windsurf). Notes for each are in Notes for each tool.
- A plan with room for about 25 to 40 messages: the 18 prompts, plus a few follow-ups to fix details. Free plans usually run out before the end.
- A web browser to open
Prompts.html.
What is in the pack
Section titled “What is in the pack”| Folder or file | What it is for |
|---|---|
Prompts.html |
Open this first: every prompt with a Copy button, the screenshots to attach, and your progress |
prompts/ |
The same prompts as Markdown files (01-foundation.md … 18-finish.md) |
references/ |
Screenshots of every page layout: home-desktop-1.png (1200 px wide, top to bottom), home-tablet-1.png (810 px) and home-phone-1.png (390 px wide, strips side by side) |
content/ |
The demo text as JSON: site.json, pages/*.json, collections/*.json |
assets/ |
images/ (placeholders at the right sizes, the client logos and the Instagram icon), icons/, and icon-light.png, icon-dark.png and apple-icon.png, the browser tab icons |
checklist.md |
Section heights per page, for agents that can measure what they built |
The order of the prompts
Section titled “The order of the prompts”| # | Prompt | What it builds |
|---|---|---|
| 1 | Foundation | The project, the design tokens (colours, text styles, spacing, motion), the rules for breakpoints, images and the contact form, and the icons |
| 2 | Components | Buttons and their rolling labels, the service tags, menu links, arrow links and footer link lists, the logo, the work, service, post and testimonial cards, the hamburger, the counter, the check list, rich text, the ticker, the word-by-word title, the spinner, the appear and rise effects, section labels and titles, the page-title block, form fields, choice chips and the submit button — everything the pages are made of |
| 3 | Layout | Header (with Home’s two bars and the phone menu) and footer, and the site details (site.json) |
| 4–6 | Content | The collections: the 4 works, the 4 services, the 10 testimonials, the 12 posts and the 2 legal pages |
| 7–17 | Pages | One prompt per page layout: Home, About, Work, Work item, Services, Service, Blog, Post, Contact, Legal, 404 |
| 18 | Finish | Browser titles and descriptions, share image, tab icons, sitemap and robots, a last check of every page |
Each prompt builds on the ones before it, so keep the order. A work’s, a service’s and a post’s own pages come after their list pages, and every page reuses the cards and blocks of prompt 2.
With a chat builder
Section titled “With a chat builder”
- Open
Prompts.htmland choose Lovable, Bolt, v0, Replit at the top. - Start a new, empty project in your tool.
- Copy prompt 1. In the tool’s message box, attach the screenshots listed on the card (drag them from the
referencesfolder, or use the attach button), paste the prompt and send it. - Wait until the tool has finished and the preview works. Compare it with the screenshots; if something is off, ask for that one fix in a short message (“On desktop, the Contact button should sit at the right end of the header, as in the screenshot”).
- Tick the prompt in
Prompts.htmland go on with the next one.
Before the page prompts, add the pack’s placeholder photos to the project: upload the assets/images folder into
public/images/. The prompts expect them there, and the pages only take the right shapes once they are.
The Content prompts (4–6) are long on purpose: they carry the text of every work, service, testimonial, post and legal page. Send them as they are. The tool saves the files and shows nothing new yet — that is expected.
Some page prompts list more screenshots than a tool takes in one message (Home has six desktop slices and three phone images, About five and two). Attach the desktop ones first; if your tool has a limit, send the rest in a short follow-up (“Here are the phone screenshots for the same page”).
With a coding agent
Section titled “With a coding agent”- Copy the whole pack into your project folder and name it
catchup/. - Open
Prompts.html, choose Cursor, Claude Code, Codex, Windsurf at the top, and copy the kickoff prompt. - Send it to the agent. It copies the content, the images and the icons into the project, then works through the prompts in order, opening the screenshots for each page. The Content prompts are skipped — the files are already there.
- Check each page as it lands, in the browser, at phone and desktop width. Agents that can run a browser can also
compare their result with
catchup/checklist.md.
Checking a page
Section titled “Checking a page”- Put the site next to the page’s screenshots at 1200, 810 and 390 px wide: same sections, in the same order, with the same alignment and spacing.
- Resize the window slowly from phone to desktop: the layout changes at 810 px and 1200 px and never scrolls sideways.
- On a computer, hover the buttons, menu links, service tags, the work, service and post cards, the award rows, the team members and the footer links. On Home, reload in a new tab to see the intro, point at the works in the hero, and watch the logos and testimonials move and the numbers count up; on a service page, switch between Per Project and Per Month; on Blog, scroll until all the posts have loaded; send the contact form in demo mode.
Photos are grey placeholders until you add your own — see Making it yours.