Troubleshooting — Kendi 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, Latest posts stand in a column of stacked cards; the screenshot has rows”). 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 Content prompts with the posts (prompts 4–12, about 33,000 to
37,000 characters each), the foundation (prompt 1, about 31,000) and Home (prompt 14, about 29,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.
The header menu and the footer are empty after prompt 3. That is expected: the Categories menu, the footer’s Categories column and the Instagram photos read the collections that the Content prompts (4–13) save.
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, or a card is taller than the others. Upload the pack’s assets/images folder into
public/images/ before the page prompts: the placeholders carry each photo’s size. A photo box sized by a ratio must
clip (overflow: hidden), or a photo of another shape stretches it; ask the tool to add it.
The header scrolls away. It shouldn’t: Kendi’s header is a white bar fixed at the top of the window on every page, over a spacer of its height. On phones the open menu grows the bar over the page without pushing it down.
The sidebar doesn’t stay in view. On desktops it sticks 120 px under the top of the window while the post or Home’s
main column scrolls past, and stops at the end of its section. It is often taller than the window, so its lower blocks
show as the column ends. Below 1200 px it follows the main column on purpose. A parent with overflow: hidden stops a
sticky element: ask the tool to use overflow: clip there.
Articles shows only six posts. It loads six more each time you scroll near the end, up to all of them; a spinner shows while the next six appear.
The page change doesn’t animate. That is by design: a link swaps the page at once and lands at the top.
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 hovers change at once, the slideshows don’t step on their own and the menus open at once, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.
The browser tab still says Kendi. The home page’s title is meta.title in pages/home.json; the other pages end
in “ | Kendi”, except posts, which show their own title. 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: /blog/<slug>, /category/<slug>, /author/<slug> and /legal/<slug>. If only the three posts whose
titles hold “’” fail, the tool compares the encoded address with the slug: ask it to decode the address first.
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. An address without a dot after the @ shows it too.
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 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 posts, authors, team and sponsored ad are sample content — replace them with your own.
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.