Skip to content
Sign inJoin waitlist

Troubleshooting — Brickfolio 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 laptops, the profile card should be 350 wide and 60 px from the projects, 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 Home’s first part (prompt 8, about 40,000 characters), the Content prompts 6 and 7 (about 37,000 and 34,400) and the foundation (prompt 1, about 29,000). If your tool refuses a Content prompt, split it in two at a post boundary, or upload the pack’s content folder into src/content/ instead.

Too many screenshots for one message. Attach the laptop screenshots with the prompt and send the phone ones in a follow-up; the tablet and desktop ones are optional (Getting started).

Only part of Home is built. Home comes in two prompts: prompt 8 builds the profile card and the sections down to the contact form, prompt 9 adds the questions. Send both before you check the page.

Fonts look different, or lines break at other words. The site uses Inter (400, 500 and 700, the accent words in 700 italic) at normal letter spacing, with its optical size fixed at 14 on the whole page; without that, small text runs wider. Ask the tool to load Inter with its optical size axis from Google Fonts or Fontsource and to set font-variation-settings: "opsz" 14 on the body, as prompt 1 describes. The code in the posts uses Fragment Mono.

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 photos on the cards are grey even after I added mine. The project and post cards show their photo at 50 % grey until you hover them, as in the design. Once an image has loaded, the grey box behind it must go: if a placeholder colour shows around a photo, ask the tool to remove it “as prompt 1 describes”.

The header looks wrong. The header is an Ink bar on every page, sticky at the top (70 / 85 / 100 / 100 tall), and never changes with the scroll; the page starts right under it. On phones “Menu” opens the links and “Hire Me” under the logo and the bar grows; “Close” closes it. The header links lead to Home’s sections and stop below the bar. Ask the tool to fix it “as prompt 3 describes”.

The profile card doesn’t stay in view. From 1000 px up the profile card sits beside the page and sticks 150 px (160 from 1440) from the top of the window until the end of the column; below 1000 it is the first block, full width, with a grey line under it. A parent with overflow: hidden stops it from sticking. Ask the tool to follow the Sidebar section in prompt 8.

The footer is full width, or the copyright shows twice. The footer is the last block of the page column, after a thin divider, not a full-width band. On Home from 1440 up the copyright line moves into the profile card and the footer shows only the newsletter box; the project and post pages show it at every width, and the 404 has no footer. Ask the tool to follow the footer’s Layout table in prompt 3.

The roles don’t change, or jump back. The line under your name moves up to the next role every four seconds and loops without a visible jump back. With “reduce motion” switched on in your system settings it stays on the first role on purpose. Otherwise ask the tool to follow the Rotating roles component in prompt 2.

The testimonials or the logos don’t run, or jump. Both rows run to the left without end (the testimonials slower), their edges faded; hovering doesn’t stop them. Ask the tool to follow the Ticker component in prompt 2.

More than one question opens. One question is open at a time, the first on load; opening another closes it. Ask the tool to follow the FAQ accordion in prompt 2 and the Questions section in prompt 9.

Home shows only four projects or four posts. That is by design: “More Projects” adds the last two projects, and “More Posts” four more posts at a time, newest first.

“Download CV” gives a 404. The link is /cv.pdf: copy the pack’s assets/cv.pdf (or your own CV) to public/cv.pdf.

Hover effects don’t show on a phone. They are for devices with a mouse or trackpad, as in the design; the service cards’ moving photos start at 810 px.

Motion is missing. With “reduce motion” switched on in your system settings, the roles, the tickers and the service photos stand still and the menu and the questions open without movement, on purpose. Nothing appears on scroll, no number counts up, and pages change without a transition, as in the design. Otherwise ask the tool to add the motion “as the prompt describes” for that section.

The browser tab still says Brickfolio. Home’s title is site.title; the other pages end in “ | Brickfolio”. 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> 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. A red outline on a contact field means it is empty or the e-mail is 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.

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, the profile photo and the tab icons included. The client logos (Logoipsum placeholders), the icons and a sample CV are included.

Is there a blog page, a category page or a privacy page? No. Brickfolio’s pages are Home, a page for each project and each post, and 404; the articles are listed on Home. Add a page with a prompt in the style of the page prompts (Making it yours).

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.