Skip to content
Sign inJoin waitlist

Troubleshooting — Marai Neesu 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 project cards are stacked in one column; the screenshot has two per 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 first two Content prompts (prompts 4 and 5, about 35,000 characters each), Home (prompt 9, about 28,000) and the foundation (prompt 1, about 25,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: 400 for the large statements, paragraphs and form fields, 500 for headings, labels and buttons. Ask the tool to load Manrope from Google Fonts or Fontsource as prompt 1 describes (from Fontsource the family is called “Manrope Variable”) and use it everywhere.

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 disappears when I scroll down. On desktops that is the design: scrolling down fades the bar’s background, the logo and the Contact button, and leaves only the frosted pill of links floating over the page; scrolling up brings them back. Tablets and phones keep a solid bar. If it hides on smaller screens too, or the links’ pill fades as well, ask the tool to fix it “as prompt 3 describes”.

Nothing animates when I scroll. On purpose: Marai Neesu has no load, scroll or page-change animations. The motion is in the hovers, the rolling roles, the testimonials’ belt, the service photos, the course modules and the questions.

Motion is missing. With “reduce motion” switched on in your system settings, the belts and photo strips stand still and moves happen at once, on purpose; the two slideshows still step every 4 seconds. Otherwise ask the tool to add the motion “as the prompt describes” for that section.

Hover effects don’t show on a phone. They are for devices with a mouse or trackpad, as in the design. On phones the service photos roll by themselves and the testimonials become a slideshow with arrows.

The Blog shows only six posts. The rest appear when you press “Load More” under the list. Every post is in the page from the start, so search engines and links see them all.

The clock in the footer shows another time. It shows the time in footer.timeZone (Asia/Dubai), not the visitor’s: set your own time zone and city in site.json.

The browser tab still says Marai Neesu. The home page’s title is site.title; the other pages end in “ | Marai Neesu”. 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: /project/<slug>, /product/<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.

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, and screenshots of Marcframe’s own templates; the pack uses placeholders at the same sizes. The tool logos name real tools — show the ones you use — and the client logos are placeholder 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.