Define workspace and project knowledge

1. 1

   Decide if your instructions apply to all projects in your team or just one specific project.

   This determines where you should put your instructions: 'workspace knowledge' for team-wide rules, or 'project knowledge' for single-project details.

2. 2

   For team-wide rules (like coding styles or preferred tools), go to 'Settings' then 'Knowledge' (or 'Project settings' then 'Knowledge') and add your instructions to the 'Workspace knowledge' field.

   This makes sure Lovable applies these rules to every project in your workspace automatically, saving you from repeating them.

3. 3

   For rules specific to a single project (like what the app does or its database details), go to 'Project settings' then 'Knowledge' and add your instructions to the 'Project knowledge' field.

   This helps Lovable understand the unique aspects of that particular project, making its suggestions more accurate.

4. 4

   Write your instructions clearly, using bullet points and direct rules, as if you're explaining it to a new team member.

   Clear and concise instructions help Lovable understand and follow your rules more effectively.

5. 5

   Review and update your knowledge periodically if your project or team's rules change.

   Keeping your knowledge up-to-date ensures Lovable always works with the most current information.

I need to set up persistent instructions for Lovable. I want to define shared coding standards for all my projects and specific context for my current project. Can you guide me on how to add this 'workspace knowledge' and 'project knowledge'?

Workspace knowledge

A set of instructions or rules that apply to all projects within your team's Lovable account. Think of it as your team's shared handbook for how code should be written.

Project knowledge

A set of instructions or context specific to one particular project. This tells Lovable what your app does, how it's built, or special terms it uses.

Skills

Pre-made or custom instructions that Lovable uses only when you ask for a specific type of task, like writing a customer email or running a checklist. Unlike knowledge, skills aren't always active.

• Don't put project-specific details in workspace knowledge, as it will apply to all projects unnecessarily.
• Avoid vague instructions like 'Write clean code'; be specific about what 'clean' means (e.g., 'Always enable TypeScript strict mode.').
• Don't forget to update your knowledge if your project's rules or architecture change, or Lovable might follow outdated instructions.
• Don't exceed the 10,000 character limit for either workspace or project knowledge.
• Don't expect Lovable to always follow instructions perfectly in very long conversations if the instructions are buried deep in a lot of context.