Knowledge: what Devin should remember

Here's an annoyance you've probably already hit. You told Devin your team uses the internal ui-kit library in your prompt. Next session, you have to say it again. And again. Every recurring instruction becomes a tax on every session.

Knowledge solves this. It's a collection of instructions (tips, conventions, workflows) that Devin automatically recalls when relevant. If you've typed the same instruction into three prompts, it should probably be knowledge.

Every knowledge item has two parts:

1. The content: the instruction itself.
2. The trigger description: a plain-English description of when Devin should pull it in.

How does knowledge get created? You can create it by hand (Settings & Library → Knowledge → Create knowledge), but the better path is one you saw at the end of 101: Devin suggests knowledge from your feedback in chat. You review the suggestion, edit it or ask Devin to regenerate it with your feedback, and approve.

A few controls worth knowing:

• Scope / pinning: pin an item to no repo (retrieved when relevant), a specific repo (always used there), or all repos.
• Macros: give an item a !shortcut to pull it in explicitly from any prompt.
• Enable/disable: disabling is per-user and non-destructive; it stops firing in your sessions without deleting it for the team.
• Folders: group items by team, project, or workflow; bulk enable/disable a folder; or let Devin auto-organize.

Best practices: keep each item targeted at one workflow (split big ones up, since Devin can retrieve multiple at once), make triggers specific to the content, aim for items relevant to roughly 70–80% of sessions in their scope, and prune, because stale knowledge can mislead.