Champion kit

This page is for the engineer who already uses Claude Code and wants their team to get the same benefit. Tooling rarely spreads because of an announcement. It spreads because one person uses it well, talks about it in the open and makes it easy to copy. That is what a champion does, and it costs far less time than people expect.

The job in three parts

Time budget

Agree this with your lead so it stays a multiplier on your work, not a second job as a helpdesk.

Show your work

What is worth posting

Post techniques someone can reuse tomorrow, not finished outcomes. "I shipped X" is a status update; "here is how I got it to do X" spreads. Some that have landed well on teams I have worked with:

• "You can @ a whole folder. I asked which handlers in @api/routes/ had no input validation and it found three."
• "I put Claude in plan mode before touching the billing code. It laid out every file it wanted to change, and I struck one off before it started."
• "Added a Stop hook that plays a sound when it finishes. Kicked off the migration and made a coffee. Config in thread."
• "/init wrote our CLAUDE.md in thirty seconds. I added the 'never touch vendor/' rule and it has respected it since."

Where to post

Keep it short

A screenshot and a line, or a quick before and after, is the right size. People copy short posts and bookmark long ones, and bookmarks are where good ideas go to die. Write in your own voice; these are just for length and tone:

TIL @-mentioning a directory works. Asked which files in @services/payments/
had no tests and it listed four. Two of them handle refunds.

Plan mode is why I'm happy using this on shared code. Shift+Tab until it
says "plan" and it tells you exactly what it wants to change first.

Be the person people ask

Reply with the prompt

The best answer to "how did you get it to do that?" is the prompt itself.

Them: How did you get it to spot the deadlock?

You: I said "The job in @workers/sync.py hangs under load, find out why".
It found two locks taken in opposite orders. Try the same wording on yours.

Point at the feature, not the manual

"Press Shift+Tab until you see plan" helps more in the moment than a link. If they want depth they will find it.

Questions you will get

Make it self-sustaining

You are not running a programme. Success is the day questions in the channel get answered by someone other than you.

Skills covers the skill format if you have not written one yet.

A 30-day plan

Loose, and adjust to taste.

Week 1: seed it. Create the channel, pin the Quickstart, post two or three of your own examples with the prompts. Working if: a few reactions and at least one question.

Week 2: set a rhythm. Start the Friday thread, answer everything in public, share one skill or CLAUDE.md snippet. Working if: someone else posts their own example.

Week 3: pair and consolidate. Offer two or three short pairing sessions and turn the most common questions into a pinned FAQ. Working if: the same people keep coming back rather than trying once.

Week 4: hand over. Recruit a second champion and send your lead or admin a short note on what is and is not working. Working if: other people are answering questions.

When someone wants more

You are the warm introduction, not the training course. Once a colleague is past "should I bother?" and into "how do I get good at this?", send them to the Quickstart, Common workflows and Best practices.

Handling sceptics

Scepticism about tools that touch code is healthy. Do not argue the general case. Acknowledge it, reframe briefly, and offer one demonstration on their own code. Most concerns dissolve after one good experience.

Cheat sheet to pin

Tip: Claude Code ships often. Check anything version-specific against this handbook before you share it widely.

Related

• Communications kit
• Best practices
• Skills
• Hooks guide
• Common workflows