Skip to content
Sign inJoin waitlist

Getting started — Tustel AI Prompts

The pack builds Tustel 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 20 to 30 messages: the 16 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 … 16-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 contact form, the logo files and the icons
2 Components Buttons, menu and text links, the logo, the hamburger, section and page titles, the appear and text effects, project and post cards, the slideshow, the counters, the ticker and the specialities card, the paged list, rich text, form fields and the submit button — everything the pages are made of
3 Layout Header (its two looks, the second bar on Home and the phone menu) and footer, and the site details (site.json)
4–7 Content The collections: clients with their logo files; projects, services and testimonials; the posts (in two parts)
8–15 Pages One prompt per page layout: Home, About, Portfolio, Project, Blog, Post, Contact, 404
16 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.

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 Book a call 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.

The Content prompts (4–7) are long on purpose: they carry the demo text of every project, service, testimonial and post, and the client logos. Send them as they are. The tool saves them as files and shows nothing new yet — that is expected. So is the white header on the light home page after the Layout prompt: the Home prompt puts the photo under it.

Some page prompts list more screenshots than a tool takes in one message (Home has six desktop slices and two phone images, Project five and two). 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 tustel/.
  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 tustel/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.
  • Hover the buttons, menu links, cards and social links on a computer; on Home, scroll past the client logos and back up to see the solid header fade in; switch the portfolio between Catalog and List on desktop and point at the titles; choose another service; use the testimonial arrows; scroll the Portfolio and the Blog until more cards load; send the contact form in demo mode.

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