3 rules for a vibe coding team in one Git repo

3 vibecoders, 1 repo, 0 chaos: the rules and our CLAUDE.md

An AI agent can write two hundred lines in a minute. Without rules, one bad prompt goes straight to your customers. These three rules let three people work in one repository with Claude Code while the live site stays safe.

Part 1 open with your account Full program 7 modules Time About 2 hours for part 1

Why AI makes team rules more important

With AI, every developer types less and changes more. That is great until three agents edit the same files, or one push of half tested code reaches the live site. The problem is not the agent. It is a repository without rules.

Two words first. main is the branch with what is live right now. develop is where everything new lands first and is tested on a staging copy of the site.

Rule 1. Two branches that never mix

main is what is live. develop is where everything is tested first. Nobody pushes to main, ever. Code reaches main only after it works on the staging copy.

main

develop

feature/TASK-42

Task branches start from develop and come back through a pull request. Only a tested develop goes into main.

Rule 2. One task, one branch, one pull request

Every task gets its own branch from develop, named feature/TASK-number-short-name. Our task board creates that name automatically, and every task links to its pull request, so you always see what is waiting for review.

And every developer's Claude gets its own worktree: a separate checkout of the repository on its own branch. Two agents never edit the same files.

Rule 3. One shared CLAUDE.md and a review gate

The team rules live in CLAUDE.md in the root of the repository. Claude reads it at the start of every session, so every agent on the team follows the same rules. Claude reviews every pull request. A human merges. Secrets never go into the repository.

That is how three people ship fast, and the live site stays safe.

Set up the repository for three developers

What part 1 covers

The setup prompt
The CLAUDE.md template
One Claude per developer: worktrees
The review gate
Release to main

Create your account to open part 1

Enter your email and click the activation link we send you. Part 1 opens right away, at no cost.

Team repository, full program

Part 1 gives you a working first version. The full program takes it all the way to a setup you can run every day.

From task board to branchBranch names from task numbers, and every task linked to its pull request.

Staging for developAn automatic deploy of develop to a test copy of the site.

Checks before reviewTests, build and a secret scan on every pull request.

Conflicts without panicUpdating a task branch from develop and resolving conflicts with Claude.

Releases and rollbackRelease pull requests, tags and going back fast when something breaks.

Secrets.env out of git, encrypted backups and what to do after a leak.

A new developer's first dayAccess, CLAUDE.md, the checklist and a first small task.

PriceThe price is shown here before payment opens.

Get the full program

Sources

Common workflows: worktrees, Claude Code docscode.claude.com/docs/en/common-workflows

Worktrees, Claude Code docscode.claude.com/docs/en/worktrees

Memory and CLAUDE.md, Claude Code docscode.claude.com/docs/en/memory

About protected branches, GitHub Docsdocs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches

Questions and answers

Do we need GitHub for this?

The rules work with any Git host. The commands in this guide use GitHub and its command line tool gh, because branch protection and pull requests are set up there in a few lines.

Why not let Claude merge the pull requests?

Because a person must own what goes live. Claude reviews, explains and fixes. A human reads the review and presses merge. That one rule stops a confident agent from shipping its own mistake.

Is one approving review enough for three people?

For a small team, one approving review plus Claude's review is a good balance between speed and safety. When the team grows or the code handles payments or personal data, raise it to two.

What happens if someone pushes to main by mistake?

With branch protection on and admins included, GitHub refuses the push. The developer opens a pull request into develop instead, which is exactly the habit you want.

More Claude Code guides

EVAAbout 3 hours for part 1

Eva: an AI ads manager for Meta ads

Step by step guide to Eva, an AI ads manager in your team chat: Meta ads reports, cost per qualified lead and rules that work like a specialist.

Part 1: open with your accountFull program: 7 modules

DASHBOARDAbout 3 hours for part 1

A Facebook ads dashboard in kroner

Build a one link Facebook ads dashboard with Claude Code: spend, leads, cost per lead and cost per qualified lead in kroner, token safe on the server.

Part 1: open with your accountFull program: 6 modules

FACTS5 minutes to read, part 1 about 1 hour

Opus 5.5: facts and fakes, with sources

Is Opus 5.5 really on the Free plan? When did it come out? Four fakes and six facts about Claude Opus 5.5, each checked on Anthropic's own pages.