Knowledge Base

The Knowledge Base is a place to store context, instructions, and reference information that the AI uses whenever it generates content for your project. It's the most effective way to make the AI produce results that are specific to your product, brand, or requirements.

What is the knowledge base for?

By default, the AI only knows what you tell it in each conversation. The knowledge base lets you store persistent information that carries across every interaction — so you don't have to repeat yourself.

Examples of what to put in the knowledge base:

• Brand guidelines — Your brand's name, color palette, fonts, tone of voice
• Product context — What your product does, who it's for, key features
• Technical requirements — Technology stack, coding conventions, libraries to use or avoid
• Content guidelines — Preferred terminology, things to always or never say
• Audience information — Who the end users are, their experience level, their goals

Adding knowledge base content

1. Open your project
2. Click the Project Settings icon (gear) in the workspace toolbar
3. Click the Knowledge tab in the Project Settings sidebar
4. Type or paste your content into the editor
5. Click Save Changes

The knowledge base supports plain text. Write it as if you're briefing a new team member — clearly and specifically.

How the AI uses the knowledge base

Every time you send a message in the chat panel, the AI reads the knowledge base first. It uses that context to:

• Write code or content that matches your brand and requirements
• Avoid technologies or patterns you've flagged as off-limits
• Use correct terminology and naming conventions
• Make design decisions aligned with your guidelines

Tips for effective knowledge base content

Be specific, not vague. "Use a warm, friendly tone — like explaining something to a smart friend, not a formal document" is more useful than "casual tone."

Include examples where possible. "Our CTA buttons always say 'Get started' not 'Sign up'" gives the AI concrete direction.

Update it as your project evolves. If you change your stack, rebrand, or shift your product direction, update the knowledge base to reflect that.

Keep it focused. You don't need to include everything — just the information the AI would otherwise get wrong or miss without explicit guidance.

Knowledge base vs. chat messages

	Knowledge Base	Chat Messages
Persists across sessions	Yes	No
Applies to every generation	Yes	Only that conversation
Best for	Stable context and guidelines	Specific one-time instructions

Use the knowledge base for anything you'd want the AI to always remember. Use chat messages for specific requests in the moment.