Getting started — Lookis AI Prompts
The pack builds Lookis 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 20 to 30 messages: the 13 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 … 13-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 logo), icons/, and icon-light.png, icon-dark.png and apple-icon.png, the browser tab icons |
checklist.md |
Section heights per page, for agents that can measure what they built |
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 contact form, the logo file and the icons |
| 2 | Components | Buttons and their rolling labels, menu links and filter tabs, the arrow link, the logo, the arrow circles, the hamburger, labels and section titles, the two-column page shell, project cards, service rows and cards, testimonial and award cards, the numbers, the numbered lists, rich text, the ticker, the testimonial slideshow, the gallery, the word-by-word text, the list that loads on scroll, the questions, the clock, form fields and the submit button — everything the pages are made of |
| 3 | Layout | Header (with the clock and the phone menu) and footer, the site details (site.json) and the copy shared by several pages (pages/shared.json: the testimonials and the “See what I do” band) |
| 4 | Content | The collections: the 16 projects and the 4 services |
| 5–12 | Pages | One prompt per page layout: Home, About, Portfolio, Portfolio item, Services, Service, Contact, 404 |
| 13 | 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 Testimonials and “See what I do” sections that Services, a service page, About, Portfolio and Contact reuse.
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 clock should sit at the left end of the header, 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 prompt (4) is long on purpose: it carries the text of every project and service. Send it as it is. 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 six desktop slices and three phone images, Portfolio 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”).
With a coding agent
Section titled “With a coding agent”- Copy the whole pack into your project folder and name it
lookis/. - 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 prompt is 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
lookis/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.
- 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, project cards, service rows, service and award cards, gallery photos and footer links; on Home, watch the name run across the top, the introduction appear word by word and the testimonials move on every few seconds; on Portfolio, switch the tabs and scroll until all the projects have loaded; open a few questions on Services; send the contact form in demo mode.
Photos are grey placeholders until you add your own — see Making it yours.