MasterMaster
Back to main site
Build

Project knowledge

Knowledge is persistent context that the agent knows in every message.— brand guidelines, technical rules, user persona, prohibitions.

Overview

Without Knowledge, you have to repeat "use dark theme", "always in English" in every prompt. With Knowledge, you write it once and the agent respects it forever.

What to put in Knowledge

  • Brand guidelines — primary color, typography, tone of communication.
  • Agent rules — "never use console.log in production".
  • Persona — who the target user is.
  • Architectural decisions.
  • Prohibitions — what is absolutely not allowed in the project.
Do not put secrets or API keys in Knowledge. They belong in Secrets.

How to set up Knowledge

  1. Open Settings → Knowledge.
  2. Write the rules in markdown.
  3. Save. The change will take effect in the next message.

Knowledge example

markdown
# Project knowledge

## Brand
- Primary color: #6366F1
- Display font: Space Grotesk, body Inter
- Tone: friendly, English

## Agent rules
- Everything in English (UI texts and comments)
- No inline colors — use tokens from index.css
- Animations via framer-motion

## Prohibitions
- Never change src/integrations/supabase/types.ts