Define reusable instructions with skills

1. 1

   Go to your 'Workspace settings' and then 'Skills'.

   This is where you manage all the custom instructions Lovable can learn and use.

2. 2

   Choose how you want to add a new skill: 'Build with Lovable' to have Lovable guide you, 'Write manually' to type it yourself, 'Import from GitHub' to pull from a code repository, or 'Upload a ZIP' for a file.

   You have several options to create a skill, depending on your preference and where your instructions are stored. You can also save a successful chat interaction as a skill directly from a project chat.

3. 3

   For a new skill, give it a short, unique name (like 'launch-checklist'), write a clear description starting with 'Use when...' that tells Lovable exactly when to use it, and then provide the detailed instructions Lovable should follow.

   The name is how you or Lovable will refer to it. The description is crucial for Lovable to know when to apply the skill automatically. The instructions are the playbook Lovable will follow.

4. 4

   If you want Lovable to automatically use the skill when it recognizes a matching task, ensure 'Automatic use' is turned on for that skill (it's on by default).

   This allows Lovable to proactively apply your custom instructions without you having to ask every time.

5. 5

   To use a skill manually, type '/' in your project chat, select the skill from the list, and then type your request.

   This tells Lovable to specifically use those instructions for your current task, even if it wouldn't have applied them automatically.

Lovable, I want to create a new skill. It should be named 'release-notes-draft', and you should use it when I ask you to 'draft release notes' or 'summarize new features for a release'. The instructions are: 'Draft release notes for our latest software update. Focus on user-facing changes and improvements. Use clear, concise language. Start with a catchy headline, then list key features with a short explanation for each. Conclude with a call to action for users to update. Do not include internal technical details or bug fixes unless they directly impact the user experience. The tone should be enthusiastic and informative.'

Workspace

Your main account area in Lovable, where all your projects and shared settings live.

Skill

A set of reusable instructions you teach Lovable for specific tasks, like a mini-playbook.

Knowledge

General rules and information that Lovable always keeps in mind for every message, like your company's brand guidelines.

Slash command

A special instruction you type in chat starting with '/', like '/skill-name', to tell Lovable to do something specific.

Bundled files

Extra files, like templates or reference documents, that you can attach to a skill for Lovable to use alongside its main instructions.

• Do not make skill descriptions too vague, or Lovable might not use the skill when you expect, or it might use it for unrelated tasks.
• Avoid putting instructions that should apply to every message into a skill; those belong in 'Knowledge' instead.
• Do not try to make one skill do too many things; split broad guidance into focused skills for better results.
• Remember that skill names cannot be changed after creation; if you need to rename one, you'll have to delete and recreate it.
• Do not forget to review and update your skills; outdated instructions can lead to incorrect or unhelpful responses from Lovable.