Dev Guide
Your team’s conventions, baked in. Release process, repo structure, branch protection. Every team has rules. Branch naming. Where repos go. How releases work. What gets committed and what doesn’t. The problem is keeping everyone aligned… especially when some of your team members are AIs that start fresh every session. The Dev Guide is the single document that covers all of it. Best practices for teams where humans and AIs ship real software together.What It Covers
- Branching. Branch prefixes per agent, forced worktrees, no commits on main.
- Repo structure. The
ai/folder standard, private/public pattern, where everything lives. - Release process. Merge, deploy, install. Three steps, never combined, never skipped.
- License compliance. Dual-license model, CLA requirements, copyright enforcement.
- Multi-agent workflow. How multiple AIs work on the same codebase without stepping on each other.
- The
ai/folder standard. Plans, notes, ideas, dev updates, todos. One structure for every repo.