Welcome to context management

In 101 you ran the loop: prompt in, PR out. This course is about what separates a team that's using Devin from a team that's good at Devin. The answer, mostly, isn't better prompts. It's better context.

Think of Devin as a new engineer on your team. A new hire is smart on day one but doesn't know your conventions, your internal libraries, or your deploy quirks. So you onboard them, and that investment compounds. Devin is no different. Out of the box, DeepWiki has already scanned your repos and built a knowledge graph of your codebase. That's why teams typically start around a 70% PR acceptance rate with no tuning at all. The teams that climb into the 80 to 90% range get there by layering on the two building blocks this course teaches, Rules and Skills, and managing them with Plugins.

Good context also saves you money. Every convention Devin doesn't know turns into a corrective follow-up, and follow-ups mean longer sessions and more ACUs. Teach Devin something once and you stop paying to repeat it in every session after.

By the end of this course you'll know how to write a rule, turn a repeated instruction into a skill, choose who a skill is for, and decide which one to reach for when.