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.

Here's the mental model. When a new engineer joins your team, they're smart on day one, but they don't know your conventions, your internal libraries, your deploy quirks. You invest in onboarding, and they compound. Devin works the same way. 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 three mechanisms this course teaches: Knowledge, Playbooks, and Skills & Rules.

There's a second payoff: cost. Every convention Devin doesn't know is a corrective follow-up you'll have to send, and follow-ups mean longer sessions, which means more ACUs. Context management is ACU management. Teach it once, stop paying for it every session.

By the end of this course you'll have built all three mechanisms with your own hands in the sandbox, and you'll know exactly which one to reach for when.