Anthropic publishes Champion Kit for Claude Code adoption

Anthropic has published a Champion Kit for individual engineers who already use Claude Code and want to help their team adopt it. The guide is structured around three behaviors intended to fit inside a normal working week, with explicit time budgets.
Three champion behaviors
- Share what you discover — post the prompts, screenshots, and small wins in the channels your team already reads. Reusable techniques (e.g., “I learned that @-mentioning…”) compound across the team; status updates do not.
- Be the person people ask — when a colleague asks how you did something, respond with the actual prompt you used so they can apply it directly. A concrete, runnable example removes the gap between curiosity and first successful use.
- Grow the circle — establish lightweight recurring habits like a dedicated channel or weekly thread so momentum continues even when you’re busy.
Weekly time budget
The guide recommends no more than ~40 minutes total per week, distributed as:
- Posting wins and prompts — about 15 min. Capture in the moment with a screenshot and one or two sentences; avoid formal write-ups.
- Answering questions in a shared channel — about 20 min. Answer publicly once, then link back to that answer when the question recurs.
- Hosting a weekly show-and-tell thread — about 5 min. The champion posts an opening prompt; the team supplies the content.
- Optional pairing or walkthroughs — 0 to 30 min, reserved for colleagues who are genuinely blocked. Offer the Quickstart link before scheduling time.
Common concerns and one-liners
The kit includes responses to frequent objections, for example when someone asks about Claude Code’s data access or cost. The recommended format is a quick-reference sheet rather than long documentation.
The full source includes the full thirty-day playbook and a link to the complete documentation index at https://code.claude.com/docs/llms.txt.
📖 Read the full source: HN AI Agents
👀 See Also

Using the Dispatcher Pattern to Reduce Claude API Costs by 95%
A developer reduced their Claude API costs from $800-$2,000/month to about $215/month by implementing a dispatcher pattern that delegates heavy work to Claude Code CLI on a Claude Max subscription, while using minimal API tokens for orchestration.

OpenClaw Workspace Configuration Lessons from Two Months of Use
A developer's experience with OpenClaw shows that workspace quality impacts agent performance 5-10x, with specific guidance on SOUL.md, AGENTS.md, MEMORY.md, USER.md, and skills configuration.

iOS Developer Shares Claude Code Best Practices After Shipping Multiple Apps
An iOS developer with cybersecurity background outlines specific practices for using Claude Code effectively, including environment separation, observability setup, and avoiding technical debt accumulation.

Resolving Disconnection Issues in OpenClaw Control UI
Learn how to solve the 'Disconnected (1008): control ui requires HTTPS or localhost' error when using OpenClaw on a Hostinger VPS.