Project Knowledge

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Project Knowledge working in a real project rather than a sandbox.

   Set up Project Knowledge in this project — project-specific agent context — schema, terminology, persona (10K chars). Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Onboarding the agent to a domain

   The record lists this as one of the jobs Project Knowledge is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Project Knowledge for onboarding the agent to a domain. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Project Knowledge is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Project Knowledge before I publish. Check project-specific persistent context and 10,000-character capacity, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Schema and terminology stability

   A second job the record lists for Project Knowledge, useful once the first path works.

   Extend this project so Project Knowledge also covers schema and terminology stability. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Project Knowledge?

  Project Knowledge is Lovable's Workspace feature: Project-specific agent context — schema, terminology, persona (10K chars). Project Knowledge stores app purpose, schema, domain terminology, and architectural decisions for a single project.

• Is Project Knowledge GA or in beta?

  Project Knowledge is generally available (GA) on Lovable.

• What Lovable plan includes Project Knowledge?

  Project Knowledge is available on all Lovable plans.

• When did Project Knowledge launch?

  Project Knowledge launched on Apr 25, 2025.

• Global Project SearchSame category, also GA · Jun 2025
• Business PlanSame category, also GA · Aug 2025
• User Roles and PermissionsSame category, also GA · Aug 2025