Skip to content
Sign inJoin waitlist

Getting started — Denzel AI Prompts

The pack builds Denzel 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 25 to 35 messages: the 15 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 … 15-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, three strips side by side, each continuing the one before)
content/ The demo text as JSON: site.json, pages/*.json (home, blog, not-found), collections/*.json (posts, categories, authors)
assets/ images/ (placeholders at the right sizes, the logo and widget-background.png, the sidebar’s dotted world map — a real image, not a placeholder), icons/ (Facebook, Twitter, Instagram, Pinterest and the search glass), 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, the two fonts, text styles, spacing, motion), the rules for breakpoints, images and the form, the logo and the icons
2 Components The section, divider and layout with sidebar, section titles, breadcrumbs, the logo, menu links, the search button, the menu icon, the pill button, social icons, the newsletter form, post meta, post photos, the post cards in all their looks, the post slider, rich text, the sidebar widgets and the search dialog — everything the pages are made of
3 Layout Header (with the phone menu), the search dialog and the footer, and the site details (site.json: menu, search words, socials, sidebar and footer)
4–8 Content The collections: 5 categories and 6 authors, then the 26 posts in four parts
9–14 Pages One prompt per page layout: Home, Blog, Category, Author, Post, 404
15 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 sidebar (About, Recent and Explore Topics) that the Category, Author and Post pages reuse, and the Category prompt builds the list of posts beside the sidebar that the Author 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 footer’s three columns should be 40 px apart, each under a black 1 px line, 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 images 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 the logo and the sidebar’s world map, which are real images.

The Content prompts (4–8) are long on purpose: they carry the categories, the authors and the full text of every post. Send them as they are. The tool saves the files and shows nothing new yet — that is expected.

Some page prompts list several screenshots (Blog has three desktop slices and three phone images). 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 denzel/.
  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 denzel/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 in windows 900, 1000 and 844 px tall.
  • 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 menu links, the search button, the social icons, the post cards (their photos settle from 110 % to 100 %) and the “View All” links. On Home, watch the slider move one card every five seconds; open the search and type a word; on a phone width, open and close the menu; in the footer, sign up in demo mode.

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