Project knowledge

Every project has a Knowledge tab: standing instructions the AI reads on every build of that project. Use it for anything you'd otherwise have to repeat, like your brand voice, your audience or rules the design must follow. It's also where Buildliy keeps what it remembers about your app and the parts you've asked it to keep as they are.

Open the Knowledge tab

In your project, click the Workspace menu at the top right of the workspace, then choose Knowledge. The tab is titled Standing instructions for every build.

Write your instructions

1. 1

   Type your instructions

   Write plain sentences or a short list in the box. There's no special format.

2. 2

   Click Save knowledge

   Your instructions apply from the next build onwards. Discard throws away unsaved changes.

Good things to put in Knowledge:

• Voice and tone: how your text should sound.
• Visual rules: colours to use or avoid, how much white space, icon style.
• Audience: who the app is for and what they know.
• Business facts: your business name, opening hours, service area.
• Constraints: things the AI should never do.

For example:

Business: Juniper Yoga, a small studio in Leeds. Open 7am to 9pm, every day.
Audience: beginners, many over 50. Avoid jargon.
Tone: warm and calm. Address the reader as "you". No exclamation marks.
Design: sage green and cream. Never bright blue. Generous white space.
Never put more than two buttons in the hero section.

A few things to know:

• Your message wins. If something you ask for in chat conflicts with Knowledge, the chat request takes priority.
• There's a limit of 8,000 characters. The counter under the box turns amber as you get close.
• Don't put passwords or API keys here. Knowledge is plain text that goes to the AI on every build. Save keys in Secrets and API keys instead.
• On a team, the project's owner and Admins can edit Knowledge. Other teammates can read it but not change it.

What I remember about your app

After your project's first successful build, if your Knowledge is still empty, Buildliy fills it in with a short summary of what you told it. It appears under the heading What I remember about your app: and can include what the app is, who it's for, business details, style and tone, the colours and fonts you picked, the pages, and your sign-in and payments choices.

Every line comes from your own answers; nothing is made up. A note above the box says Written by Buildliy from your answers — edit anything. Change or delete any line as you like. If a line disagrees with something you ask for later, the newer request wins.

This means a change you ask for days later still matches your audience, style and business details instead of drifting back to something generic.

Keep a part exactly as it is

When you're happy with a specific part of a page, such as a headline, a button or a photo, you can tell the AI not to touch it.

1. 1

   Select the part

   Click the arrow icon to the right of the address bar above your preview, then click the part. See Edit by clicking.

2. 2

   Click Keep as is

   On the chip that appears above the chat box, click Keep as is. You'll see Kept — the AI won't change this.

This adds a line under Keep as is: in your Knowledge, for example:

Keep as is:
- Main heading on / ("Fresh bread daily") — app/page.tsx

In later builds, the AI is instructed not to change, restyle, move, rename or remove that part unless your message asks to change that exact part. Everything else on the page can still change. If a request can't be done without touching a kept part, the AI is told to do the rest and say which part it left alone. For a hard block on a whole file, use a file lock instead.

To let the AI change it again, delete its line in the Knowledge tab and click Save knowledge. Because Keep as is writes to Knowledge, on a team it's available to the project's owner and Admins.

Lock files

You can also lock a whole file of your app's code, so the AI can't change it at all.

1. Open the Code tab.
2. Hover over a file in the file tree and click the small lock icon next to it.
3. The lock stays visible and the file name turns italic. The AI's changes to that file are blocked in every build.
4. Click the lock again to unlock it.

On a team, the project's owner and Admins can lock and unlock files. See View and download your code.

Use Keep as is for things you can see on the page. Use file locks when you or a developer have a file that must stay exactly as written.

How careful the AI should be

Below your instructions, the Knowledge tab also has a How careful should I be? card. It decides how often the AI stops to ask you before changes that affect customers, money or data. It applies from your next build. See Plans and approvals.

Related

• Edit by clicking
• View and download your code
• Write great prompts
• Design and themes