Skip to content
Sign inJoin waitlist

Getting started — Fitbricks AI Prompts

The pack builds Fitbricks 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.

  • 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 40 to 50 messages: the 27 prompts, plus a few follow-ups to fix details. Free plans usually run out before the end.
  • A web browser to open Prompts.html.
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 … 27-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 logos, the category symbols, the store badges and the social marks), icons/, icon.svg (the browser tab icon) and apple-icon.png (the home-screen icon)
checklist.md Section heights per page, for agents that can measure what they built
DESIGN.md The design tokens and style rules in one file, for coding agents
# Prompt What it builds
1 Foundation The project, the design tokens (colours, text styles, spacing, motion), the rules for breakpoints, images and the three forms, the logo files, the social marks and the icons
2 Components Buttons, text links and card actions, the menu links and the hamburger, the category links, the club, program, trainer and post cards, the feature, info, app, testimonial and pricing cards, the store badges, the list that loads on scroll, the FAQ row, rich text, the ticker, carousel and quote slider, the video, and the forms’ fields, radios and submit button — everything the pages are made of
3 Layout Header (fixed, transparent over the photo pages, the tablet and phone menus) and footer with its Instagram photos, and the site details (site.json)
4–9 Content The collections: the clubs, legal pages and cities, the programs, trainers, facilities and program categories, then the posts with their full text
10–26 Pages One prompt per page layout: Home (two prompts), About, Programs, Program, Program category, Clubs, Club, City, Trainers, Trainer, Free trial, Contact, Blog, Post, Legal, 404
27 Finish Browser titles and descriptions, share image, tab and home-screen icons, sitemap and robots, a last check of every page

Each prompt builds on the ones before it, so keep the order. Some page prompts reuse a section written in an earlier one (“The CTA band section from prompt 11 — reuse it”): the CTA band comes from Home (prompt 11), the Trainers band from About (prompt 12), the program list from Programs (prompt 13), the clubs list from Clubs (prompt 16) and the club locations from the Club page (prompt 17).

  1. Open Prompts.html and choose Lovable, Bolt, v0, Replit at the top.
  2. Start a new, empty project in your tool.
  3. Copy prompt 1. In the tool’s message box, attach the screenshots listed on the card (drag them from the references folder, or use the attach button), paste the prompt and send it.
  4. 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 Claim free trial button should sit in its own white panel at the right end of the header, as in the screenshot”).
  5. Tick the prompt in Prompts.html and 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–9) are long on purpose: they carry the full text of every club, program, trainer and post, and the legal pages, cities, facilities and program categories. Send them as they are. The tool saves them as files and shows nothing new yet — that is expected. So is one thing after the Layout prompt: the footer’s Programs column and legal links stay empty until the Content prompts have saved the collections.

Some page prompts list more screenshots than a tool takes in one message (Home has eight desktop slices and five phone images). 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”).

  1. Copy the whole pack into your project folder and name it fitbricks/.
  2. Open Prompts.html, choose Cursor, Claude Code, Codex, Windsurf at the top, and copy the kickoff prompt.
  3. 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.
  4. 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 fitbricks/checklist.md.
  • 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 menu links (they fill orange), the buttons, the club and program cards (“See Details” rises in), the trainer cards, the post photos (they zoom), the footer links and the Instagram photos; scroll Home and watch the header change over the photo and the facts rise in; let the hero’s quotes change on their own; scroll the program, club, trainer and blog lists and see more load; open and close the FAQ rows; press a program’s video; send each form in demo mode; follow a link — the page changes at once, without a transition, and the header stays fixed at the top.

Photos are grey placeholders until you add your own — see Making it yours.