Getting started — Cerette AI Prompts
The pack builds Cerette 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 22 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 … 22-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 and the grain texture), icons/, and icon.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 the inquiry form, and the icons |
| 2 | Components | Buttons and their rolling labels, nav and footer links, the logo, the icons, the hamburger, project, service, post, testimonial, value and team cards, the figures, the award table, rich text, the load spinner, the services switcher, the team picker, the letter, word and line effects, the scroll appear, section titles and labels, the ruler, photos and the grain, the quote band, the call to action, the form, its fields and the submit button — everything the pages are made of |
| 3 | Layout | Header (fixed, transparent over a dark hero, with the phone menu) and footer, with the site details (site.json), the call to action’s copy and the forms’ copy |
| 4–9 | Content | The collections: 6 projects, 6 services, 6 testimonials, 12 team members, 12 posts (in three parts) and 2 legal pages |
| 10–21 | Pages | One prompt per page layout: Home (in two parts), About, Projects, Project, Services, Service, Blog, Post, Contact, Legal, 404 |
| 22 | 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. Home builds the ruler, the quote band, the testimonials, “Why Cerette” and the call to action that later pages reuse; About builds the big page title (with the small text beside it) that Projects, Services, Blog and Contact reuse; Services builds the inquiry section that a service page reuses; a project page builds the “Other Work” row that a post reuses as “Similar posts”.
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 project cards should sit three in a row with their tops aligned, 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 folder
also holds grain.png, the texture laid over the photos: keep it.
The Content prompts (4–9) are long on purpose: they carry the text of every project, service, testimonial, team member, 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, About five and three). 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
cerette/. - 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
cerette/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 with reduced motion and the entrance effects finished, so every block sits in its place; the hero shows its poster (a placeholder) instead of the film.
- 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 cards and the footer links. On Home, scroll past the hero and watch the header turn solid, and switch the services; on About, point at the team’s names; on a project page, scroll through the story’s sticky photos; on Blog, scroll to load more posts; on Contact, send the form in demo mode.
Photos are grey placeholders until you add your own — see Making it yours.