411f0b81821f06dc5b3e20ccdd993b4370304dea
- Move English README to README.en.md, add Chinese README.md as the entry point - Cross-link both READMEs at the top - Add Tagging section to docs/03-git-workflow.md (YYYYMMDD format, immutable, annotated, daily-suffix collisions) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
team-guide
中文版:README.md
Working agreements for our team's AI-assisted ("vibe coding") development. Small team, English docs, opinionated but light.
What this repo is
A single source of truth for how we work, not what we build. It covers:
- How we use Claude Code (CLAUDE.md, permissions, hooks, memory, skills)
- How we collaborate with AI when writing code (vibe coding norms)
- Git workflow (branches, commits, PRs, review)
- Skill management and project planning rhythm
- Code & deliverable style (naming, comments, READMEs, task packages, handoffs)
Every doc is short. If a rule needs more than half a page to justify, it probably isn't a rule yet — it's a discussion.
Layout
team-guide/
├── README.md ← you are here
├── CLAUDE.md ← context Claude Code loads when working in this repo
├── docs/
│ ├── 01-vibe-coding.md ← how humans + AI split the work
│ ├── 02-claude-code.md ← CLAUDE.md / permissions / hooks / memory / skills
│ ├── 03-git-workflow.md ← branches, commits, PRs, review
│ ├── 04-skills-and-planning.md ← skill catalog + planning cadence
│ ├── 05-code-style.md ← naming, comments, structure
│ └── 06-handoff.md ← task packages, handoff checklists
└── templates/
├── CLAUDE.md.template
├── README.md.template
├── PR_DESCRIPTION.template.md
└── HANDOFF_CHECKLIST.template.md
How to use it
- New team member — read
docs/01-vibe-coding.mdanddocs/03-git-workflow.mdfirst. The rest is reference. - Starting a new project — copy the templates from
templates/into the new repo and fill them in. Drop a top-levelCLAUDE.mdthat points back here. - Disagreeing with a rule — open a PR against this repo. Don't silently diverge.
Versioning
Releases are tagged by date: YYYYMMDD (e.g. 20260520). Each tag is a
snapshot of main from that day, suitable for "this is the version we
agreed to follow." See docs/03-git-workflow.md for the tagging rules.
- Latest tag: see
git tag --sort=-creatordateon the remote mainis always the working copy; tags are checkpoints
License
Internal.
Description
Team working agreements for AI-assisted development
157 KiB
0 Stars
8 Watchers
0 Forks
Languages
Shell
61.6%
Batchfile
38.4%