Skip to content
Sign inJoin waitlist

Troubleshooting — Cerette 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.

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 project cards should sit three in a row with their tops aligned, as in the screenshot”). 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 Home’s first part (prompt 10, about 38,000 characters) and the Content prompts for the projects and the posts (prompts 4, 6 and 8, about 33,000 to 34,000 each). 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.

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 Plus Jakarta Sans (600 for titles and headings, 500 for text), with Marcellus for the founder’s quote and Inter for what is typed into the form. The links, buttons and labels are an upper-case 12 px style; every style is set a little tight (−0.03em). Ask the tool to load the three fonts from Google Fonts or Fontsource and to check every text style against prompt 1.

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 photos look speckled. That is the grain texture (grain.png) laid over them at half strength, as in the design. If it shows as a grey box with crossed lines instead, the file was replaced by a placeholder: copy assets/images/grain.png from the pack again.

The hero film doesn’t play. It plays from Pexels’ address in pages/home.json; a network that blocks it shows the poster instead. Replace it with your own video (Making it yours). With “reduce motion” switched on in your system settings, the film still plays, as in the design.

The header is white text on a light page, or never turns solid. Over the dark hero of Home and a project page the header is transparent with white links; it turns the page colour once the next section’s top reaches the middle of the window. On the other pages it is solid from the start, and on the 404 page it stays transparent. Ask the tool to follow the Header’s Interactions & motion in prompt 3.

The services switcher shows all services at once. On tablets and desktops it is a row of tabs that shows one service at a time; on phones an accordion with one row open. Ask the tool to follow Home’s Services section.

The team shows everyone at once on a phone, or the desktop picker doesn’t react. On desktops, pointing at a name makes that person current and their portrait stays in place while the list scrolls; on tablets and phones a grid shows six people and six more as you scroll.

Blog shows every post at once on a phone. Blog shows a page of posts (six on desktops, four on smaller screens) and loads the next as the spinner nears the bottom of the window. Every post is in the page from the start, so search engines and links see them all.

Hover effects don’t show on a phone. They are for devices with a mouse or trackpad, as in the design.

The browser tab still says Cerette. The home page’s title is site.title; the other pages end in “ | Cerette”. 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: /project/<slug>, /service/<slug>, /blog/<slug> and /legal/<slug>. One demo project’s slug has an accent (elvaré-studio): the address keeps it.

The inquiry form says “Something went wrong”. The form service refused the request or the address is wrong: check the variable (The inquiry form), then build or publish again. If the form won’t send at all, a required choice (Project type or Project budget) is still empty: the browser points at it.

Build errors. Paste the error message to the tool and ask it to fix it before sending the next prompt.

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 Unsplash and Pexels photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The hero film plays from Pexels until you replace it.

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.