Troubleshooting — Balancee 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 case study rows should be 10 px apart with the number column 100 wide, 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 the Content prompts 5 and 7 (about 35,000 characters each), Home (prompt 9, about
26,000) and the foundation (prompt 1, about 22,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.
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 (500 for headings and buttons, 400 for text) at normal letter spacing. Ask the tool to load Inter from Google Fonts or Fontsource (as the variable font) and to check that every text style has its weight and line height, 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 white text on a photo is hard to read. The Home hero video, the call to action band and the first About cards have a black cover at 80 % (or 50 % on the About cards) over the photo or video, so the text reads on any photo. If it is missing, ask the tool to add it “as the section’s Layout table describes”.
The header looks wrong. The header is white on every page, fixed to the top, and never changes with the scroll; every page starts below a spacer of its height (60 / 71 / 75). The current page’s link is a filled Ink pill. Ask the tool to fix it “as prompt 3 describes”.
The footer is too tall or too short. The footer’s bottom row (the note and the legal links) sits 50 px under the white strip at every width, while the blocks above it are 60 / 80 / 100 apart; the strip’s service names never wrap. Ask the tool to follow the footer’s Layout table in prompt 3.
A case study row won’t open, or jumps. The rows open independently when you click anywhere on them; the first one starts open. Ask the tool to follow the Case accordion in prompt 2 and the Case Studies section in prompt 9.
The Blog page shows only four posts. It shows four at a time, then the next four as soon as the spinner under the list comes near the screen (the Portfolio page works the same way). Every item is in the page from the start, so search engines and links see them all.
The videos don’t play. They play from the Pexels website, muted: the hero loops at once, the About clip only while it is on screen, and “Watch a review” on a click. A network that blocks Pexels shows the poster only. Replace them with your own (Making it yours).
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 videos stay on their poster, the logo ticker stands still and the rows 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 Balancee. The home page’s title is site.title; the other pages end in “ | Balancee”. 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>, /portfolio/<slug>, /blog/<slug> and /legal/<slug>.
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. “Please enter a valid email address.” under the Email field means the address is missing or mistyped: that check happens before anything is sent.
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 videos included? No. The demo uses Unsplash and Pexels photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The two videos play from the Pexels website until you replace them.
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.