Troubleshooting — Lookis 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 service rows put the price under the title; the screenshot has it in the same row”). 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 prompt (prompt 4, about 36,000 characters), Home (prompt 5,
about 26,000) and the foundation (prompt 1, about 25,000). If your tool refuses the 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, weight 400 (500 for the hero’s big name and the clock), as the variable
font with its optical-size axis set to the text cut (14) in every style. Without that setting the browser picks a
tighter cut for the big headings by itself. Ask the tool to load Inter from Google Fonts or Fontsource with the opsz
axis and set the optical size 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 the hero is hard to read. The hero photo has a gradient over it, clear at the top and black at the bottom, so the introduction and the links read on any photo, as in the screenshots. If it is missing, ask the tool to add the gradient “as the Home hero’s Layout table describes”.
The header hides or changes when I scroll. It shouldn’t: Lookis’s header stays stuck to the top, white, on every page, and only the thin line under it scrolls away. Ask the tool to keep it in place “as prompt 3 describes”.
The clock shows the wrong time. It shows the time in owner.timeZone of site.json (America/New_York in the
demo), not the visitor’s own: set your time zone there (Making it yours). It is
empty for a moment while the page loads, on purpose.
The Portfolio page shows only four projects. It shows four at a time, then the next four each time the spinner under the list comes near the screen. Every project is in the page from the start, so search engines and links see them all. A tab shows the projects of one service.
Hover effects don’t show on a phone. They are for devices with a mouse or trackpad, as in the design. The project cards on tablets and phones always show their title over the photo.
Motion is missing. With “reduce motion” switched on in your system settings, the name ticker and the testimonials stand still, the introduction fades in without rising and the questions open at once, on purpose. Otherwise ask the tool to add the motion “as the prompt describes” for that section.
“Book a session” opens cal.com. That is the demo’s placeholder: put your booking page (or /contact) in
hero.primary in pages/home.json, footer.action and bookingHref in site.json.
The browser tab still says Lookis. The home page’s title is site.title; the other pages end in “ | Lookis”. 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 /services/<slug>.
The contact 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.
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 Unsplash and Pexels photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes.
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.