Skip to content
Sign inJoin waitlist

Troubleshooting — Metuo 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 plans should sit in a row of three with their tops aligned; the screenshot has the Green one in the middle”). 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 7, about 38,500 characters), the second Content prompt (prompt 5, about 37,500) and the foundation (prompt 1, about 33,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 Manrope (500 for headings, 400 for text, 600 for buttons) with a letter spacing of −0.03em in every text style. Ask the tool to load Manrope from Google Fonts or Fontsource and to check that every text style carries its letter spacing, 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, the photo titles, the founder quote and a post’s cover have a gradient over the photo, clear at the top and black at the bottom (--gradient-veil), 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 stays white (or stays see-through). Over the photo at the top of Home, About, Service, Testimonial and Blog the header is see-through with White text; it turns solid when the next section reaches the middle of the window. Contact, a post, a legal page and the 404 have no photo at the top: their header is solid from the start. Ask the tool to fix it “as prompt 3 describes”.

The footer covers the last section, or jumps. The footer starts 200 px higher and comes down into place as you reach the end of the page, coming out from behind the last section: the page’s content is painted above it, on the page background. Ask the tool to follow the footer’s Interactions & motion in prompt 3.

The story card or the story stack doesn’t stick. Sticky positioning stops working when a parent of the card hides its overflow. Ask the tool to “use overflow: clip instead of hidden on the sections around the sticky card”.

The Blog page shows only six posts. It shows six at a time, then the next six as soon as the spinner under the list comes near the screen. Every post 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, only while they are on screen; a network that blocks Pexels shows an empty band. 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 hero doesn’t grow in, the parallax, the growing video and the rising footer stay still, the photo strips stop 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 Metuo. The home page’s title is site.title; the other pages end in “ | Metuo”. 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> and /legal/<slug>.

The booking form says “Something went wrong”. The form service refused the request or the address is wrong: check the variable (The booking form), 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.

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.