Troubleshooting — Fitbricks 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 club 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 Home’s first part (prompt 10, about 39,000 characters), the Content
prompts (4–9, about 17,000 to 36,000 each), the foundation and the components (prompts 1 and 2, about 31,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 footer’s Programs column and legal links are empty after prompt 3. That is expected: they read the collections that the Content prompts (4–9) 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 Manrope, weights 400 to 800. Ask the tool to load it from Google Fonts or
Fontsource (@fontsource-variable/manrope, which names the family “Manrope Variable”) and use it for every text, 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, or hides the top of the page. It shouldn’t: Fitbricks’ header is a bar fixed at the top of the window on every page. Over the full-window photos (Home, Free trial, the programs, 404) it is transparent and the photo starts under it; on every other page it is white and the page starts under a spacer of its height. On tablets and phones the open menu grows the bar over the page without pushing it down.
The header doesn’t change while scrolling Home. On the photo pages it switches to its scrolled look once you scroll down a little (desktops: the logo fades out; tablets and phones: a white bar with the dark logo) and back when you scroll up. Ask the tool to follow the scroll direction “as the Layout prompt describes”.
A list shows only its first cards. The program, club, trainer and blog lists load the next cards each time you scroll near their end, up to all of them; a spinner shows while they 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; on tablets and phones the cards show their “See Details” from the start.
Motion is missing. With “reduce motion” switched on in your system settings, the hovers change at once, the reveals fade without moving, the ticker stands still and the menus and FAQ open at once, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.
A program’s video is a grey box. The screenshots show it that way; in the site it is the YouTube video’s thumbnail,
and a press starts the player. Check the program’s video link if the thumbnail stays empty.
The browser tab still says Fitbricks. The home page’s title is site.title in site.json; the other pages end in
“ | Fitbricks”. 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: /program/<slug>, /program-category/<slug>, /club/<slug>, /city/<slug>, /trainer/<slug>,
/blog/<slug> and /legal/<slug>. If only /program/ride-(cycling) fails, the host or the router treats the
parentheses specially: ask the tool to match the slug as it is.
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 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 app screens too. The gym, its programs, clubs, trainers and posts 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.