Team Context Sync

A shared context protocol for teams using Claude Code. Stops developers from accidentally working on the same files or repeating each other's architectural decisions.

What happens without this

Sarah tells her Claude session: "Don't touch payments/, I'm mid-refactor." Mike opens his Claude session, asks it to fix a bug in payments/. Neither session knows about the other. Two hours later there's a merge conflict and at least one of them made changes that conflict with the refactor.

The same problem happens solo across sessions. "Don't touch the legacy API until the migration is done" evaporates when the session ends.

What's in the kit

team-context-sync/ ├── skills/ │ └── team-context.md # Claude skill — reads and updates shared context ├── templates/ │ └── team-context.md # Starter file to commit to your repo ├── hooks/ │ └── pre-commit-context-check.sh # Warns before committing off-limits files └── README.md

How it works

A team-context.md file lives in your repo root, committed to git. It has four sections: who's actively working on what, what's off limits and why, recent architectural decisions, and notes.

Each Claude session reads it at start. Before working on anything, Claude checks the task against active work and off-limits entries. At session end, Claude updates the file and commits it with [skip ci] so it doesn't trigger pipelines.

Git handles the sync. No infrastructure, no server, no shared account.

Commands inside Claude Code

"Sync context" — read team-context.md and summarize what's active
"Update context: I'm working on auth/" — add or update your entry
"Mark off limits: payments/ because Sarah is mid-refactor" — add a warning for the team
"Show conflicts" — check your planned work against active entries
"Log decision: switched from axios to fetch" — add a timestamped decision

Setup

cp templates/team-context.md team-context.md
git add team-context.md && git commit -m "Add team context"

mkdir -p .claude/skills
cp skills/team-context.md .claude/skills/

Add to CLAUDE.md:

At session start: read team-context.md and summarize active work.
Before starting tasks: check team-context.md for conflicts.
At session end: update team-context.md with what you worked on.

Share the same setup with everyone on your team. Five minutes per developer.

$24

One-time download. Instant access.

Download Team Context Sync

Use LAUNCH for 20% off

Questions: zac@builtbyzac.com