Skip to content
Sign inJoin waitlist

Troubleshooting — Tustel 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 services list puts the photo under the summary; 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 half of the posts (prompt 6, about 34,000 characters) and the foundation (prompt 1, about 29,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, weights 400 and 500, 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).

The header is white on a light page, or solid over the photo. On Home and the 404 page it lies over the photo, transparent with white content, and scrolls away with the page; every other page has one solid header that hides as you scroll down and comes back when you scroll up. Until the Home prompt adds 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 solid header never shows on Home. It fades in only while you scroll back up past the client logos, and not near the top of the page. If you removed the client logos, ask the tool to tie it to the section under the hero instead.

The services list shows several services. One is chosen at a time, the first at the start: a click or a tap chooses another, and so does pointing at a name on desktop; on phones the chosen one opens under its name and the one before closes. Ask the tool to fix it “as the Home prompt describes”.

There is no Catalog / List switch on a phone or tablet. That is on purpose: the switch and the List view are for desktops; tablets and phones show the grid of cards.

The Portfolio or the Blog shows only six items. It shows six at a time on desktops, four on tablets and phones: when you scroll down to the spinner under the list, the next ones appear. Every item is in the page from the start, so search engines and links see them all.

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 and the tickers stand still, the counters show their final number and the texts don’t rise, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.

“Book a call” opens cal.com. That is the demo’s placeholder: put your booking page (or /contact) in bookCall.href in site.json.

The browser tab still says Tustel. The home page’s title is site.title; the other pages end in “ | Tustel”. 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: /portfolio/<slug> and /blog/<slug>.

A project card or gallery photo has the wrong shape. Covers and gallery photos keep their own proportions, so a tall photo makes a tall card: crop the photo to the shape you want (Making it yours).

The form says “Something went wrong”. The form service refused the request or the address is wrong: check the variable (The contact form), 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 included? No. The demo uses Unsplash photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. 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.