Notes for each tool — Fitbricks AI Prompts
The prompts work in any tool that writes and runs a React website. They ask for React with TypeScript, Tailwind CSS and Motion, and leave the framework to the tool: Vite with React Router in Lovable, Bolt and Replit, Next.js in v0, and the project you start them in for coding agents. Tools change often; if a step below looks different, the idea stays the same.
Chat builders
Section titled “Chat builders”Lovable
Section titled “Lovable”- Start a new project and send prompt 1 as the first message, with its screenshots attached.
- Lovable keeps the whole project in view, so later prompts can say “the CTA band section from prompt 11” and it finds it.
- Connect GitHub (in the project settings) early if you want a copy of the code outside Lovable.
- The forms: set
VITE_FORM_ENDPOINTas described in The forms, or ask Lovable to store the submissions in its database instead.
- Start with prompt 1 in a new project; attach the screenshots to each message.
- Bolt’s preview shows errors as they happen — when one appears, ask Bolt to fix it before the next prompt.
- Instead of the Content prompts (4–9), you can upload the pack’s
contentfolder intosrc/content/; upload theassets/imagesfolder intopublic/images/either way.
- v0 builds with Next.js. Send prompt 1 in a new chat, then the rest in the same chat, with their screenshots.
- If a chat grows too long, v0 may lose track of earlier prompts: start the next prompt with “Continue the Fitbricks site in this project; the foundation and components already exist.”
- Instead of the Content prompts, you can add the pack’s
contentandassetsfiles to the project.
Replit
Section titled “Replit”- Use Replit’s Agent in a new React (Vite) app; send the prompts in order with their screenshots.
- Ask the Agent to run the app after each prompt and check the preview.
Coding agents
Section titled “Coding agents”Cursor, Claude Code, Codex, Windsurf and similar agents read files, so they don’t need the Content prompts or the screenshots pasted in:
- Create an empty folder (or an empty Next.js or Vite project) and copy the pack into it as
fitbricks/. - Send the kickoff prompt from
Prompts.html(choose Cursor, Claude Code, Codex, Windsurf at the top). - Let the agent work through
fitbricks/prompts/one prompt at a time, and review each page as it lands.
Agents that can open a browser (for example with a browser or Playwright tool) can compare their pages with the
screenshots in fitbricks/references/ and the section heights in fitbricks/checklist.md. fitbricks/DESIGN.md gives them
the colours, text styles and rules in one file.
If you prefer another stack — Astro, SvelteKit, Vue — say so in the kickoff prompt: the prompts describe the design, not the code. A framework that builds every page ahead (Next.js, Astro) also gives each program, club, trainer and post its own share tags and the 404 page a real 404 status.
ChatGPT, Claude or Gemini in a chat window
Section titled “ChatGPT, Claude or Gemini in a chat window”A chat assistant without a project can write the code, but you would have to put the files together and run them yourself. Use a builder or an agent instead; if you already work in a chat assistant’s project or canvas, send the prompts in order as with a builder.