Troubleshooting — Compose Digi 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 project cards should sit three in a row with their tops aligned, as in the screenshot”). 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 foundation (prompt 1, about 33,000 characters) and the Content
prompts for the posts (prompts 7–9, about 31,000 to 33,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.
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 DM Sans (500 for headings, 400 for text) with Inter for the footer’s big service names. The links, buttons and dates are an upper-case 13 px style with a little letter spacing (0.03em); the big titles are tighter (−0.04em). Ask the tool to load both fonts from Google Fonts or Fontsource and to check every text style against prompt 1.
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 footer’s band of service names is empty. It shows the names from the services collection, which arrives with the Content prompts (4–10). Before them, the band is empty on purpose.
The cursor dot is missing, or shows on a phone. The custom cursor is for devices with a mouse: it follows the pointer over the page content, hides over the header and the footer, and never shows on touch screens or on Contact, a post’s text and the 404. Ask the tool to follow the Cursor component in prompt 2.
The rows of cards or names don’t move. The hero’s project cards, About’s client logos and the footer’s service names run sideways forever at a constant speed. With “reduce motion” switched on in your system settings they stand still, on purpose.
A project page’s photos don’t move. The project’s photos slide and grow into place and lag a little behind the page as you scroll, and the testimonial fades in. Ask the tool to follow the section’s Interactions & motion in the Project prompt; with reduced motion they sit still at their end place.
Load More shows everything at once, or never goes away. Projects and Blog show a few cards at a time (more on larger screens), Careers four openings; each click shows the next page and the button is gone once all are shown. Every item is in the page from the start, so search engines and links see them all.
The video doesn’t play. It plays from YouTube in a player that opens over the page; a network that blocks YouTube shows an empty player. Replace it 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 browser tab still says Compose. The home page’s title is site.title; the other pages end in “ | Compose”. 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: /services/<slug>, /projects/<slug>, /careers/<slug> and /blog/<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. A message under a field (“Please enter a valid email address.”) means that field 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.
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 and the video included? No. The demo uses Unsplash and Pexels photos, which can’t be sold unmodified; the pack uses placeholders at the same sizes. The About video plays from YouTube until you replace it.
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.