Skip to content
Sign inJoin waitlist

Getting started — KorDent AI Prompts

The pack builds KorDent 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 20 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 … 20-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/, icon.svg (the browser tab icon) and apple-icon.png (the home-screen icon)
checklist.md Section heights per page, for agents that can measure what they built
DESIGN.md The design tokens and style rules in one file, for coding agents
# Prompt What it builds
1 Foundation The project, the design tokens (colours, text styles, spacing, motion), the rules for breakpoints, images and the four forms, the logo file and the icons
2 Components Buttons, the logo, the icons and the service line icons, chips and section titles, the appear effects, the service, post, review and outcome cards, the dentist’s parts, the accordion, the filter tabs, the search field, the hamburger, rich text, form fields, the star rating, the submit button, the choice cards and the booking form, the contents list of a service page — everything the pages are made of
3 Layout Header (the white bar and the phone menu) and footer with its newsletter, and the site details (site.json)
4–8 Content The collections: departments, facts, advantages, reasons, dentists, reviews and outcomes; the services (in two parts); the posts; the legal pages
9–19 Pages Home in two prompts (9 and 10), then one prompt per page layout: About, Services, Service, Blog, Post, Legal, Contact, Book, 404
20 Finish Browser titles and descriptions, share image, tab and home-screen icons, 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 services, About, the outcomes, the dentists and the reviews; the second adds the call to action with the clinic video and the blog below them. Send both before you judge the page.

  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 Appointment 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–8) are long on purpose: they carry the demo text of every department, dentist, review, outcome, service, post and legal page. Send them as they are. The tool saves them as files and shows nothing new yet — that is expected. So is one thing after the Layout prompt: the footer’s Dental Services links lead to the 404 page until the service pages exist (prompt 13).

Some page prompts list more screenshots than a tool takes in one message (Home has seven desktop slices and four phone images, Services six and four). 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 kordent/.
  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 kordent/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 cards and post cards; on Home, filter the services by department and search them, scroll the outcomes and watch the index follow, switch the dentist tabs (an accordion on phones) and pick stars in the review form; on Services, open the first-visit steps; on a service page, follow the contents card as you scroll; on Book, choose a treatment and see the dentists change; send each form in demo mode; scroll any page and see the header go with it; follow a link — the page changes at once, without a transition.

Photos are grey placeholders, and the clinic video shows its poster, until you add your own — see Making it yours.