Skip to content
Sign inJoin waitlist

Troubleshooting — Semono 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 service rows put the list under the text; the screenshot has it beside it”). 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 first part of Home (prompt 8, about 37,000 characters), the foundation (prompt 1, about 36,000) and the Content prompts 5 and 6 (about 35,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.

Home is only half built after prompt 8. That is expected: Home comes in two prompts. Prompt 9 adds the sections from “Why choose” down to the blog.

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, weight 500 (400 in the form fields), as the variable font with its optical-size axis: the headings use its Display cut. Ask the tool to load Inter from Google Fonts or Fontsource with the opsz axis, use it everywhere and set the optical size of each text style 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 header is white on a light page, or light over the photo. On Home and the 404 page the header lies over the photo, transparent with white content; on Home it turns light once the About section reaches the middle of the window. Every other page has a light header over a spacer of its height. Until the Home prompts add the photo, the home page’s white header sits on the light background — that is expected. Otherwise ask the tool to fix it “as prompt 3 describes”.

The header hides when I scroll. It shouldn’t: Semono’s header stays fixed at the top on every page. Ask the tool to keep it in place “as prompt 3 describes”.

The Services, Testimonial or Blog page shows only a few items. They show four at a time (the Blog six on desktops), then the next ones each time the spinner under the list comes near the screen. Every item is in the page from the start, so search engines and links see them all.

A video doesn’t play. The demo’s clips play from Pexels’ servers; a blocked network or a removed clip leaves the poster. 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. The service rows react to the pointer on desktops only.

Motion is missing. With “reduce motion” switched on in your system settings, the texts and blocks don’t rise, the logo ticker stands still, the menu and the accordions open at once and pages change without the transition, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.

The page change doesn’t animate. It uses the browser’s view transitions, which some browsers don’t have yet: there the page simply changes. Ask the tool to check it in a recent Chrome, Edge or Safari.

“Book a free consultation” opens cal.com. That is the demo’s placeholder: put your booking page (or /contact) in process.book.href in pages/home.json.

The browser tab still says Semono. The home page’s title is site.title; the other pages end in “ | Semono”. 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>, /career/<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.

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 photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The two videos play from Pexels and are only examples. The client logos are drawn samples — replace them with your clients’.

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.