Troubleshooting — KorDent AI Prompts
AI tools rarely get every detail right the first time. These answers cover the usual drifts from the design and the questions buyers ask most.
Problems you may hit
Section titled “Problems you may hit”The result doesn’t look like the screenshots. Point at the difference in a short follow-up: name the section, the breakpoint and what you see (“On desktop, the service cards stand in two columns; the screenshot has three”). One fix per message works better than a list. If a page is far off, ask the tool to rebuild just that section “exactly as described in the prompt”.
The tool forgot an earlier prompt. Long chats lose detail. Start the prompt with a reminder — “The design tokens and components from the earlier prompts already exist; reuse them” — or paste the relevant part of prompt 1 or 2 again.
“Message too long”. The longest prompts are the components (prompt 2, about 39,500 characters), the foundation
(prompt 1, about 38,000), the first part of Home (prompt 9, about 37,700) and the first Content prompt for the services
(prompt 5, about 37,000). If your tool refuses a Content prompt, split it in two at an item boundary, or upload the
pack’s content folder into src/content/ instead.
Home is only half built after prompt 9. That is expected: Home comes in two prompts. Prompt 10 adds the call to action with the clinic video and the blog.
Too many screenshots for one message. Attach the desktop screenshots with the prompt and send the phone ones in a follow-up (Getting started).
Fonts look different. The site uses Inter, weights 400 to 700, as the variable font with its optical-size axis held
at 14 on the whole page, so the big headings keep the text cut. Ask the tool to load Inter from Google Fonts or
Fontsource with the opsz axis and set font-variation-settings: "opsz" 14 on the body, as prompt 1 describes.
Photos are grey boxes. That is by design: the pack ships placeholders. Add your photos to public/images/ with the
same file names (Making it yours).
Photos have the wrong shape. Upload the pack’s assets/images folder into public/images/ before the page
prompts: the placeholders carry each photo’s size.
The header stays at the top when I scroll. It shouldn’t: KorDent’s header is a white bar that scrolls away with the page on every page, and never changes look. Ask the tool to make it “not fixed or sticky, as prompt 3 describes”. On phones the open menu grows the bar over the page without pushing it down.
The page change doesn’t animate. That is by design: a link swaps the page at once and lands at the top.
The clinic video shows a still picture. The demo’s clip is not in the pack, so the video shows its poster until you
add yours at public/videos/cta.mp4 (Making it yours). With “reduce motion” switched
on, it stays on its first picture on purpose.
Home shows only six services. It shows the first six that match the chosen department and the search; the Services page shows them all. Every service still has its page.
The booking form lists only one or two dentists. It shows the dentists who give the chosen treatment (the service’s
doctors). On a service page the treatment is fixed, so only its dentists are there. Check the slugs in doctors if a
dentist is missing.
“Book a treatment” doesn’t open the Book page. By design it opens the service’s own page at its booking form
(/service/<slug>#booking), with the treatment already chosen. “Book Appointment” opens /book.
Hover effects don’t show on a phone. They are for devices with a mouse or trackpad, as in the design.
Motion is missing. With “reduce motion” switched on in your system settings, the texts and blocks only fade in, the label flips and menu letters change without moving, the accordions and the menu open at once and the clinic video stays still, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.
The map shows another place. The Contact map and “Get Direction” use contact.address in site.json: write your
full address there.
The browser tab still says KorDent. The home page’s title is site.title (and meta.title in pages/home.json);
the other pages end in “ | KorDent”. Ask the tool to use site.name for that ending, then change it.
A page shows 404. Check that the item’s slug in the collection matches the address, and that the tool created
the detail pages: /service/<slug>, /blog/<slug> and /legal/<slug>. One demo post’s slug has a dot in it
(clear-aligners-vs.-traditional-braces-making-the-right-choice); if only that post fails, the server takes the dot for
a file name — ask the tool to route it, or give the post a slug without a dot.
A form says “Something went wrong”. The form service refused the request or the address is wrong: check the variable (The forms), then build or publish again.
Build errors. Paste the error message to the tool and ask it to fix it before sending the next prompt.
Questions
Section titled “Questions”Which tool gives the best result? Coding agents that can read the whole pack and run a browser follow the design most closely. Among chat builders, pick the one you already know; the prompts are the same.
Can I use another framework? Yes. The prompts describe the design, not the code — tell the tool or agent which stack to use before prompt 1.
Can I sell the site I build? You can build sites for yourself or your clients as your license allows; you can’t resell the prompts or the template itself. See License.
Are the photos and the video included? No. The demo uses photos from Unsplash and Pexels, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The clinic video is a Pexels clip in the demo and is not in the pack: add your own. The reviews, dentists and figures are sample content — replace them with your clinic’s.
Can you customise it for me, or build my site? Yes. Marcframe, the studio behind this template, updates templates to your needs (brand, content, new pages and features), builds custom templates and designs new websites. Get in touch at marcframe.com/contact or hire us on Contra.
Something is off and none of this helps. Support and updates: https://framebrick.co/support. Send the prompt number, your tool, and the error text or a screenshot: it makes the answer much faster.