team-sync
Skill1 starsChanged 14 days agoMITView on GitHub
Use when 2+ humans or AI agents work in parallel — file ownership, branching, avoiding merge conflicts, and patterns for collaborating with AI tools as a group.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Contract first: Before splitting front/back, agree the interface (route, JSON shape, function signature) in docs/STACK.md or a shared types …
- Distinctive: line 14
Sync beat: every 45 min, 3 minutes: done / doing / blocked.
- Distinctive: line 17
Done when: no two people share an unplanned file and main still runs after every merge.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Team sync (parallel humans + agents)
- Ownership map in
docs/TEAM.md: person → folders/files → current task. One owner per file. Shared files (dependency manifest, lockfile, router index,docs/PLAN.md) → announce before editing. - Contract first. Before splitting front/back, agree the interface (route, JSON shape, function signature) in
docs/STACK.mdor a shared types file. Then both sides mock against it. - Branches:
<initials>/<task>; start from freshmain; open a PR within 30–45 min; squash-merge. Pullmainbefore every task and every ~30 min. - Conflict rule: whoever merges second resolves. Never force-push
main. Nevergit add -Ablindly — stage your own files. - Agent hygiene: one agent session per branch/worktree (
git worktree add ../wt-<task> -b <branch>). Give each agent: the task, the files it may touch, the verification command. Tell it to stop and report rather than refactor neighbours. - Shared context lives in files, not chat: decisions →
DECISIONS.md, status → issue comments. Agents re-read files; they forget conversations. - Sync beat: every 45 min, 3 minutes: done / doing / blocked. Update the cut line.
- Review: skim for secrets, mocks presented as real, and anything that breaks
main. Approve fast.
Done when: no two people share an unplanned file and main still runs after every merge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

