Getting started — Balancee AI Prompts
The pack builds Balancee 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 30 to 40 messages: the 20 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 … 20-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, three strips side by side, each continuing the one before) |
content/ |
The demo text as JSON: site.json, pages/*.json, collections/*.json |
assets/ |
images/ (placeholders at the right sizes, the logo, the client logos and the LinkedIn icon), icons/, and icon-light.svg, icon-dark.svg and apple-icon.png, the browser tab icons |
checklist.md |
Section heights per page, for agents that can measure what they built |
DESIGN.md |
The design tokens and rules in one file, for building new pages in the same style later |
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 forms, the logo and the icons |
| 2 | Components | Buttons and their rolling labels, menu links, the hamburger, section titles, chips, the star rating, facts, service, post and case cards, the case accordion, step, value, detail and testimonial cards, the client logo ticker, the video player, the newsletter box, form fields, rich text, the About cards and rows — everything the pages are made of |
| 3 | Layout | Header (with the phone menu) and footer, the site details (site.json) and the copy shared by several pages (pages/shared.json) |
| 4–8 | Content | The collections: 8 services, 8 case studies, 9 posts and the 2 legal pages |
| 9–19 | Pages | One prompt per page layout: Home, About, Services, Service, Portfolio, Case study, Blog, Post, Contact, Legal, 404 |
| 20 | 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. The Home prompt builds the call to action band that About, Service, Portfolio, Case study, Blog, Post, Legal and 404 reuse, and the Services prompt builds the service cards that the Service page reuses.
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 footer’s bottom row should sit 50 px under the white strip, 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–8) are long on purpose: they carry the text of every service, case study, 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 seven desktop slices and four 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”).
With a coding agent
Section titled “With a coding agent”- Copy the whole pack into your project folder and name it
balancee/. - 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
balancee/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. The screenshots were taken in windows 900, 1000 and 844 px tall.
- 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, the header’s links, the service, post and case cards, the footer links, and on About the team cards and the award rows. On Home, open and close the case study rows and watch the logos run; on Services and Contact, send the form in demo mode; on Blog and Portfolio, scroll until all items have loaded.
Photos are grey placeholders until you add your own — see Making it yours.