Skip to content
Sign inJoin waitlist

Getting started — Semono AI Prompts

The pack builds Semono 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 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.
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, the logo and the sample client logos), icons/ and icon.svg, the browser tab icon
checklist.md Section heights per page, for agents that can measure what they built
# 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 and the icons
2 Components Buttons, the logo, the hamburger, labels and page titles, the appear and word effects, the page change, service rows, post, testimonial, step, icon, team and action cards, the video card, the figures, the logo ticker, the accordions, the lists that load on scroll, the card columns, rich text, form fields and the submit button — everything the pages are made of
3 Layout Header (its two looks, the switch on Home and the phone menu) and footer, and the site details (site.json)
4–7 Content The collections: clients with their logo files; services and testimonials; the posts (in two parts); careers, legal pages and the team
8–21 Pages Home in two prompts (8 and 9), then one prompt per page layout: About, Team, Careers, Career, Services, Service, Blog, Post, Testimonial, Contact, Legal, 404
22 Finish Browser titles and descriptions, share image, tab icon, sitemap and robots, a last check of every page

Each prompt builds on the ones before it, so keep the order. Home is the longest page, so it comes in two prompts: the first saves the page copy and builds the hero, the client logos, About and the services; the second adds the rest of the page below them. Send both before you judge the page.

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 Contact us button should sit 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–7) are long on purpose: they carry the demo text of every service, testimonial, post, position, legal page and team member, and the client logos. Send them as they are. The tool saves them as files and shows nothing new yet — that is expected. So are two things after the Layout prompt: the white header on the light home page (the Home prompts put the photo under it) and an empty Services column in the footer (it lists the services, which arrive with prompt 5).

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

  1. Copy the whole pack into your project folder and name it semono/.
  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 semono/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 buttons, menu links, footer links, service rows and post cards; on Home, scroll past the hero to see the header turn light at the About section, play and pause the video, open the reasons and switch the process tabs; scroll the Services, Testimonial and Blog pages until more cards load; open a few FAQ rows on Contact; send each form in demo mode; follow a link and watch the page change.

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