In part 1 you turned a convention into a skill and committed it. This post is about the next problem: your real setup is a skill plus a review subagent plus a build hook plus an MCP server — and every developer needs the same one. A plugin packages all of it and ships it with one install command.
Every team has conventions that live in one person’s head and spread by code review. When you use Claude Code, that knowledge quietly forks: your setup knows your rules, nobody else’s does. Skills put the convention in the repo, so the whole team — and their AI — works the same way.
Your .NET solution has 15 projects, hundreds of files, and a mountain of generated code. Claude Code’s context window isn’t infinite. Here’s how you work smartly.