Project Knowledge
Development · 8 articles
Add custom knowledge to your project
Go to Project Settings and add custom knowledge about your app's purpose, database schema, naming conventions, and architecture decisions. This helps Lovable stay consistent when making changes to your project.
Be specific
When writing project knowledge, be specific about what you want—instead of 'use a nice color scheme,' say 'use the brand colors: primary blue #0066CC, accent orange #FF6B35.' Specific instructions help Lovable make consistent decisions. Include naming conventions, exact API endpoints, database table names, and other concrete details that prevent ambiguity.
Can I add instruction files in the project's repository?
The reference material does not mention instruction files in the repository. Knowledge is managed within the Lovable editor under the Knowledge section. However, your code is synced to GitHub via the GitHub integration—you could store documentation in your repo alongside code and reference it in project knowledge. Contact [email protected] for details on advanced setups.
Can I have multiple sets of workspace knowledge instructions?
The reference material does not describe support for multiple separate workspace knowledge documents. You have one workspace knowledge section shared across all projects. If you need different rules for different teams or projects, use project-level knowledge to override or extend workspace rules. Contact [email protected] for advanced organization options.
Keep instructions concise
Shorter instructions work better than long paragraphs. Use bullet points, bold key terms, and stick to essentials. Lovable reads and applies your knowledge constraints better when they're digestible. Aim for clarity over comprehensiveness—you can always add more detail if Lovable makes a wrong decision.
What is the character limit for knowledge?
The reference material does not specify a character limit for workspace or project knowledge. For best results, keep knowledge concise and scannable. If you're unsure about limits for your use case, contact [email protected].
Which context sources does Lovable read?
Lovable reads project knowledge and workspace knowledge that you define in the editor's Knowledge section. These are the primary context sources for the AI agent. It also uses your code and components as context. The reference material doesn't mention reading instruction files from the repository or external sources. For more details, reach out to [email protected].
Write it like onboarding documentation
Frame your project knowledge the way you'd onboard a new team member. Include the app's purpose, key features, database schema overview, architectural decisions, and domain terminology. This helps Lovable understand the bigger picture and make better decisions. Think: 'If a developer was joining the team tomorrow, what would they need to know?'
