Troubleshooting — Goeboek 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 laptops, the hero’s two numbers should sit at the right of the title, 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 4, 5 and 6 (about 35,100, 35,100 and 34,200
characters), the foundation (prompt 1, about 33,400) and the components (prompt 2, about 31,800). 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 laptop screenshots with the prompt and send the phone ones in a follow-up; the tablet and desktop ones are optional (Getting started).
Fonts look different, or lines break at other words. The site uses Plus Jakarta Sans (400 to 700) for every text and Inter only for the upper-case buttons, chips and labels, at normal letter spacing. Ask the tool to load both from Google Fonts or Fontsource and to use them 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. Once an image has loaded, the grey box behind it must go: if a
placeholder colour shows around a photo, ask the tool to remove it “as prompt 1 describes”.
The logo or the thank-you drawings are missing. They are real files in the pack, not placeholders:
logo-mark.svg, success-tour.svg and success-property.svg belong in public/images/.
The header looks wrong. The header is a White bar on every page, sticky at the top (70 / 91 / 101 / 101 tall), and never changes with the scroll; the page starts right under it. Tablets show “Add Property” only; from 1200 px “Contact us” sits beside it. On phones “Menu” opens the links and both buttons under the logo and the bar grows; “Close” closes it. Ask the tool to fix it “as prompt 3 describes”.
The hero’s slideshows don’t move, or jump back. The large property cards step to the next property every 8 seconds and the testimonials every 4, looping without a visible jump back; the dots and arrows go to a slide. They play only while on screen. With “reduce motion” switched on in your system settings they stand still on purpose. Otherwise ask the tool to follow the Slideshow component in prompt 2.
The property cards don’t react on hover. On a computer, hovering a card shows its agent over the photo and steps through three photos every 1.5 seconds; on touch devices nothing changes, as in the design. Ask the tool to follow the Property card in prompt 2.
The filter is in the wrong place. From 1200 px the filter sits beside the cards and stays in view while they
scroll; below 1200 it sits above them and sticks under the top of the window while they pass. On phones only its title
and “More” show, and “More” opens the rest over the cards. A parent with overflow: hidden stops it from sticking. Ask the tool to follow the Listing filter in prompt 2 and the Layout of
prompt 9.
Properties shows only six cards. That is by design: “Load More” shows six more at a time. The Type, Location, Property category and Agent pages show all their properties at once.
A listing page is empty, or a chip leads nowhere. A property’s location, category and agent must match a
slug in locations.json, categories.json and agents.json exactly.
The tour form doesn’t open the thank-you page. After a successful send the tour form goes to /success-scheduled
and Add property to /success-add-property (the redirect of each form in the content). Check that the tool created
both pages (prompts 20 and 21).
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 slideshows stand still and the filter and the menu open without movement, on purpose. Nothing appears on scroll and pages change without a transition, as in the design. Otherwise ask the tool to add the motion “as the prompt describes” for that section.
The browser tab still says Goeboek. Home’s title is site.title; the other pages end in “ | Goeboek”. 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: /property/<slug>, /agent/<slug>, /location/<slug>, /property-category/<slug> and /blog/<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. An orange border on a field means it is empty or the e-mail is 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 visitors search or combine filters? Not in the design: each filter (for sale, for rent, a location, a category, an agent) is a page of its own. Ask your tool to add a search or combined filters once the site is built.
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 Unsplash and Pexels photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The logo mark, the thank-you drawings, the icons and the tab icons are included.
Is there an Agents page, a newsletter or a privacy page? No. Each agent has a page, reached from the property cards, the property pages and the filter; there is no newsletter form and no legal page. Add a page with a prompt in the style of the page prompts (Making it yours).
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.