Skip to content
Sign inJoin waitlist

Getting started — Compose Digi AI Prompts

The pack builds Compose Digi 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 30 to 40 messages: the 23 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 … 23-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 logo and the client logos), 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
# 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, the logo and the icons
2 Components Buttons and their rolling labels, text links, the footer’s action button, social buttons, Load More, nav links, the hamburger, the logo, the custom cursor, section titles, the divider, rich text, post, project, service, job and team cards, the ticker, the service accordion, the rating, the testimonial slider, the pricing card and its switch, the process chart, the video card, the form, its fields and the submit button, and the scroll effects — everything the pages are made of
3 Layout Header (sticky, with the phone menu), footer (the running service names, the call to action, links and contact details) and the cursor, with the site details (site.json)
4–10 Content The collections: 8 services, 8 projects, 12 job openings and 12 posts (the posts in four parts)
11–22 Pages One prompt per page layout: Home, About, Services, Service, Projects, Project, Careers, Job, Blog, Post, Contact, 404
23 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. About builds the page header (title, lead and “Scroll to Explore”) that Services, Service, Projects and Blog reuse; Home builds the dark “More” box that a project page reuses.

Reference screenshots of the home page: a desktop slice and three phone strips

  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 plan switch should sit at the right of the pricing card’s title, 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–10) are long on purpose: they carry the text of every service, project, job opening and post. 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 five desktop slices and three phone images, About and Project four or five and two or 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”).

  1. Copy the whole pack into your project folder and name it compose-digi/.
  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 compose-digi/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. The screenshots were taken with reduced motion, so the tickers stand at their start and the scroll effects of a project page sit at their end.
  • 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, the social buttons and the footer links, and watch the cursor turn into a ring or a pill. On Home, open the service rows; on a service page, switch the plan to Monthly and click the client chips; on a project page, scroll to see the photos slide and grow into place and the process bars grow; on About, play the video; on Projects, Careers and Blog, click Load More; on Contact, send the form in demo mode.

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