Adoption
Champion kit
Champion kit 这一页讲的，就是 Champion kit 这件事在 Claude Code 里到底怎么用。
页面信息
这页不是官方原文，而是顺着官方文档结构做的中文解释版。命令、参数、配置名这些硬东西尽量保留，解释部分则尽量讲成人能照着做的话。
如果你碰到特别敏感的配置、权限或企业环境差异，最好顺手点上面的“查看原始文档”再核一遍。
这一页先讲明白
这页主要讲 Champion kit：A playbook for engineers advocating Claude Code internally: what to share, how to answer questions, and how to grow adoption on your team.
你可以把它当成"Adoption"这块里专门管这一摊事的说明书。
你可以把"Champion kit"理解成 Adoption 这一栏里的一把专门工具。这页不是让你背书，而是教你什么时候该把这把工具拿出来。
原文这页大多会按 The champion role、What this should cost you、Share what you discover、What is worth sharing 这些环节往下讲。
翻成人话，大概就是：What this should cost you
第一，先别一上来全开全配。先按最小一步试通，确认没跑偏，再继续往下加。
第二，命令、配置名、参数名这些硬东西尽量保留原样。人话解释是帮你听懂，不是帮你改关键字。
第三，照着原文这几个环节挨个过：The champion role -> What this should cost you -> Share what you discover -> What is worth sharing。像下地先看水路、再试机器、再正式开干，一步一步最稳。
原页关键片段：The format that works 1
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Learned today that @-mentioning a directory works. I pointed it at
@src/components/ and asked which components were missing tests, and it
surfaced two I had forgotten about.原页关键片段：The format that works 2
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
I configured a Stop hook so I receive a desktop notification when a long
task completes. I started a refactor, stepped away, and was notified when
it finished. Configuration is in the thread.原页关键片段：The format that works 3
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Plan mode is the reason I am comfortable using this on code that matters.
Press Shift+Tab until you see "plan"; it lays out exactly which files it
intends to touch before changing anything.原页关键片段：Answer with a prompt rather than an explanation
下面这块是这一段最值钱的原文样板，先对着看一眼。
Colleague: How did you get it to find that race condition?
Champion: I asked, "The test in @tests/scheduler.test.ts is flaky, figure
out why," and it traced two unjoined promises in the scheduler. Try the
same phrasing on your test.Documentation Index
这里不是让你背"Documentation Index"这个词，而是让你看它真干活时怎么使。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
The champion role
这里主要是在交代"The champion role"这一块会碰到哪些事。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
What this should cost you
这一块主要是在说"What this should cost you"真到手上该怎么用，哪里最容易踩坑。
Share what you discover
看到这里，就把"Share what you discover"当成一件真要上手的活来看。
What is worth sharing
这段看着像个标题，其实是在说"What is worth sharing"管到哪儿。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
Where to share it
这里不是让你背"Where to share it"这个词，而是让你看它真干活时怎么使。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
The format that works
这一块主要是在说"The format that works"真到手上该怎么用，哪里最容易踩坑。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
The format that works 1
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Learned today that @-mentioning a directory works. I pointed it at
@src/components/ and asked which components were missing tests, and it
surfaced two I had forgotten about.The format that works 2
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
I configured a Stop hook so I receive a desktop notification when a long
task completes. I started a refactor, stepped away, and was notified when
it finished. Configuration is in the thread.The format that works 3
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Plan mode is the reason I am comfortable using this on code that matters.
Press Shift+Tab until you see "plan"; it lays out exactly which files it
intends to touch before changing anything.Be the person people ask
看到这里，就把"Be the person people ask"当成一件真要上手的活来看。
Answer with a prompt rather than an explanation
这一段更像在讲判断条件，什么时候该上，什么时候先别急。把触发条件看清，比背标题更重要。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
Answer with a prompt rather than an explanation
下面这块是这一段最值钱的原文样板，先对着看一眼。
Colleague: How did you get it to find that race condition?
Champion: I asked, "The test in @tests/scheduler.test.ts is flaky, figure
out why," and it traced two unjoined promises in the scheduler. Try the
same phrasing on your test.Point at the feature rather than the documentation
这一段主要是在把"Point at the feature rather than the documentation"讲实，不是只摆个标题给你看。
Questions you are likely to hear
这一块主要是在说"Questions you are likely to hear"真到手上该怎么用，哪里最容易踩坑。
Grow the circle
这里主要是在交代"Grow the circle"这一块会碰到哪些事。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
Patterns that tend to work
看到这里，就把"Patterns that tend to work"当成一件真要上手的活来看。
Thirty-day playbook
这一段更像在讲判断条件，什么时候该上，什么时候先别急。把触发条件看清，比背标题更重要。
这里还牵扯作用域，意思就是这条规则到底管当前项目、你个人，还是只管这一趟会话。
When someone wants to go deeper
When someone wants to go deeper 到底什么时候值得上，这一段就是在算这笔账。
Respond to common concerns
这里不是让你背"Respond to common concerns"这个词，而是让你看它真干活时怎么使。
看这段时要特别盯工具和权限边界，别为了省事一把全开。
Quick-reference sheet
这一段就是给你查规矩的，像看说明书那样一项项对着来。
照着做一遍
如果你不想来回翻，就先照这几步顺着做。
每做完一步就看一下结果，再决定要不要继续往下。
第 1 步：The format that works 1
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Learned today that @-mentioning a directory works. I pointed it at
@src/components/ and asked which components were missing tests, and it
surfaced two I had forgotten about.第 2 步：The format that works 2
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
I configured a Stop hook so I receive a desktop notification when a long
task completes. I started a refactor, stepped away, and was notified when
it finished. Configuration is in the thread.第 3 步：The format that works 3
"The format that works"这一段里最要紧的原始写法在下面，先看它怎么落地。
Plan mode is the reason I am comfortable using this on code that matters.
Press Shift+Tab until you see "plan"; it lays out exactly which files it
intends to touch before changing anything.第 4 步：Answer with a prompt rather than an explanation
下面这块是这一段最值钱的原文样板，先对着看一眼。
Colleague: How did you get it to find that race condition?
Champion: I asked, "The test in @tests/scheduler.test.ts is flaky, figure
out why," and it traced two unjoined promises in the scheduler. Try the
same phrasing on your test.一眼看懂这一页
先把这页到底在讲什么看明白，再去碰具体命令和配置，最不容易绕晕。
Champion kit
|
v
这是 Adoption 里的一摊要紧活
|
v
先弄懂，再下手文末提醒
这站会按官方 docs 的导航和内容变化继续重生成，原站加页、删页、改页时，这里会跟着更新。
人话解释会尽量顺着原页往下讲，但命令、参数名、配置名这些硬东西还是保留原样，免得你抄过去跑不起来。