The Waste of Locking Knowledge in One Person's Head
You worked out a super-handy prompt that gets the Agent to fix an interface correctly every time. But it lives only in your head—colleagues are still stepping in the pits you've stepped in.
The Fix: Commit It to the Repo, Share Across the Team
Commit the handy conventions/prompts to the code repo (e.g. that CLAUDE.md or a team prompt library). That way: everyone can use it, it updates with the project, and new people get it out of the box.
个人技巧（只在我脑子里）
↓ 写进仓库文件
团队规约（人人可用、跟着 git 一起进化）What to Distill: Reusable > Personal Preference
What's worth distilling is what holds for the whole team: project conventions, hard-won lessons, prompt templates proven to work.
Pure personal taste (say, your favorite phrasing) shouldn't be forced into the team conventions, to avoid bothering others.
自测 · 学完检查一下
想真正动手做题、记进度、攒连胜？到互动课里练。
What's the biggest value of sharing AI-use knowledge across a team?
答案：Avoiding everyone repeating the same pitfalls, with good experience available to all
Sharing turns individual experience into a team asset, ready out of the box even for new people.
Judge: an efficient prompt that lives only in one person's head and is never written down and shared is hard for the rest of the team to reuse.
答案：True
If the knowledge isn't written down, colleagues will keep repeating the same pitfalls and can't reuse it—exactly why it should be shared.
Which is most worth distilling into a shared team convention?
答案："Before calling our payment API, always validate the amount, with a correct example attached"
Experience that holds for the whole team and prevents pitfalls is most worth distilling; pure personal taste shouldn't be forced in.
Judge: content that's purely personal phrasing preference should also be forced into the team conventions.
答案：False
Team conventions describe "how we do it"; forcing in personal taste bothers others.
To let team conventions be reviewed, improved, and version-controlled, the most common practice is to commit them to the ___.
答案：repo
Once in the repo, the convention can be reviewed, iterated, and version-controlled just like code.
Judge: once team conventions are put into the code repo, they can be version-controlled and updated along with the project.
答案：True
The repo brings version control and collaborative review, so the conventions can evolve along with the project.