What to Paste in Lovable, v0 and Bolt So the Next Page Does Not Look AI-Made (2026)
Each builder has a place it reads on every request: Instructions in Lovable, Instructions in v0, Knowledge and agents.md in Bolt. Where each one is, what it accepts, and a short block of design rules to paste in all three.
On this page
Fixing a generated page by hand works once. The next prompt brings the defaults back, because the builder never learned your decisions.
App builders such as Lovable, v0 and Bolt make every design choice you do not state. Ask for a landing page and you get their default accent, their default font, their default feature row. You can correct it in chat, page after page. Or you can write your decisions down once, in the place the builder reads on every request.
Each of the three has such a place. They are named differently, they live in different menus, and they behave slightly differently. This article walks through each one as documented by the vendor in November 2026, then gives you one block of rules to paste in all three.
Lovable: project Instructions
Lovable renamed its Knowledge feature to Instructions. Per Lovable's documentation:
- Where: Project settings, then Instructions. Workspace instructions are under Workspace settings; personal ones under Account settings.
- Size: project, workspace and personal instructions each take up to 10,000 characters.
- Priority: project instructions generally win over workspace instructions, and personal instructions generally win over both.
- Files: Lovable also reads any
AGENTS.mdorCLAUDE.mdat the top level of the project, with every message.
Use project Instructions for the design rules of one site. If you run several client projects in one workspace, keep the shared process rules (how to name components, what to test) at workspace level and the visual identity at project level, so one client's palette never leaks into another's.
v0: Instructions
v0 has Instructions too, but they work differently. Per v0's documentation:
- Where: the + button in the prompt bar, then Instructions, then New Instruction. Each one has a title and a rule.
- Scope: they are saved to your account and available in all your chats and projects.
- Activation: you check the instructions to apply; checked instructions apply to your messages until you uncheck them, and several can be active at once.
That last point is the one to remember. An instruction you created but did not check does nothing. Create one instruction per site, named after it, and check it at the start of each session on that site.
Bolt: project Knowledge and agents.md
Bolt offers two places. Per Bolt's guide to project context:
- Project knowledge is persistent: it stays available in long conversations and is not cleared when you reset the context. It is meant for what always applies to the project, including design principles.
- agents.md: Bolt supports an
agents.mdfile in the project and uses it automatically once it is added (attach it from the plus icon in the chat box). The main instructions have to be inagents.mditself; it can link to other files.
Put the short design block in project Knowledge, and if your rules grow (token tables, component conventions), move them to agents.md and keep a one-line pointer in Knowledge.
The block to paste
The same text works in all three. It is short on purpose: well under Lovable's 10,000-character limit, and short enough to stay in a model's attention on every request. Fill in the values in angle brackets.
Design rules for this project. They apply to every page and component,
and override the defaults of the template and the component library.
Colours: background <#hex>, text <#hex>, accent <#hex>. No other accent.
Fonts: <display family> for headings, <body family> for text.
Never use:
- blue, indigo, sky, violet or purple utility classes as an accent
- gradients from blue to purple, gradient text
- Inter or Geist as the heading font
- a row of three identical cards; vary the layout between sections
- fade-up on scroll; content is visible without animation
- backdrop blur on more than one surface
- "Get started" or "Learn more" on buttons; name the action instead
- large rounded cards with heavy shadows; prefer flat with a thin border
When you change the design, change the shared theme or component,
not a single page.If you also use a coding agent on the exported code, the longer AGENTS.md design rules template carries the same decisions with the literal tokens and a working order for agents.
Choosing the values
The builders will happily fill the brackets for you, and they will fill them with their defaults. Decide them yourself:
- Accent. One colour that belongs to the brand: the logo, the product, the packaging. Not the blue the template shipped with.
- Neutrals. A background that is not pure white and a text colour that is not pure black give the page a temperature of its own.
- Fonts. A heading face and a text face that differ clearly. The pairing matters more than the individual choice.
If you have nothing yet, the free vibe-coded site checker scans your current page and proposes a palette and a type pair generated from your domain name. Copy them into the block.
Applying it to pages that already exist
The rules shape the next pages. The existing ones still carry the old defaults. Two ways to bring them over:
- One request per default. Ask the builder to apply the new accent everywhere the old blue appears, then to replace the heading font, then the card row. Small requests produce reviewable changes.
- One request per component. If the site uses a shared header, card and button, ask for those three to follow the rules; most pages update with them.
Then check: scan the published page with the AI website detector. It names each default still present, with the class it found, so you know which request to send next.
What the rules cannot do
They make the defaults less likely; they do not forbid them. A builder can still fall back to its template on a long session or when a component library brings its own theme. Expect to scan, correct and add a line to the rules a few times before the output settles.
They also do not design the site for you. They remove the choices nobody made. The choices that make a site yours (what to say first, what to show, what to leave out) are still yours to make.
Related
- I vibe-coded my site on Lovable, v0 or Bolt and it looks like everyone else's: 35 fixes for pages that already exist.
- The Anti-Slop Prompt Template: the long-form prompt behind the block above.
- Lovable in 2026, v0 in 2026, Bolt.new in 2026: what each builder starts from.
Scan your site free
Eight AI-builder defaults, the evidence for each on your page, and the fix kit. Free, no account. If your site has more pages to fix, the site report covers up to 25 of them.
Read the whole site, with a fix prompt per default
Get told when the CLI ships