Communications kit

communications-kit First recorded · 526 lines, first recorded

# Communications kit ## Launch communications ### Before you send ### The announcement ### Executive sponsor variant ### Pilot group variant ### Champion recruitment DM ## Tips and tricks campaign ### Get started ### Project memory ### Control and safety ### Connect your tools ### Automate your workflows ### Day-to-day development ### Share and scale ### Security and admin ## Quick reference ### FAQ responses ### Prompt templates

The first capture of this source. The page was already there, and this is what it said.

# Communications kit

> Launch announcements, drip-campaign messages, and FAQ responses for rolling Claude Code out to your engineering organization.

This page is for administrators and engineering leads rolling Claude Code out to a team. It provides copy-ready launch announcements, a tips-and-tricks drip campaign, and one-line FAQ responses for the questions you will be asked most.

<Note>
  Treat everything here as draft copy, not finished copy. Rewrite each message in your organization's voice, swap the example tasks for real bugs and modules from your own codebase, and replace the `[bracketed placeholders]` before sending. The announcements that drive adoption are the ones that read like someone at your company wrote them.
</Note>

## Launch communications

One announcement in two formats, plus two optional variants. Pick whichever fits your rollout and rewrite it from there.

### Before you send

Work through this checklist before the announcement goes out. Each item closes a gap that otherwise turns into a launch-day support thread.

| Item                                                                                             | Why it matters                                                                      |
| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| `#claude-code` channel created and linked in the message                                         | Gives questions one place to land                                                   |
| Install command tested on at least one machine in your environment                               | Catches proxy or firewall issues before everyone hits them at once                  |
| Security and data-handling link ready ([Data usage](/docs/en/data-usage) or your internal equivalent) | "Where does my code go?" will be the first reply                                    |
| One concrete first task chosen, a real bug or file in your codebase                              | Generic examples don't convert; "fix the flaky test in `auth_test.go`" does         |
| A named owner for the channel for the first 48 hours                                             | Unanswered launch-day questions kill momentum                                       |
| A C-suite sponsor lined up to send or co-sign the announcement                                   | Exec-sent launches consistently see higher first-week adoption than admin-sent ones |

### The announcement

Use this as your standard org-wide rollout message. It covers what Claude Code is, gives a two-minute install path, hands readers one concrete task to try, and answers "where does my code go?" before anyone has to ask.

<Tabs>
  <Tab title="Email">
    ```text theme={null}
    Subject: Claude Code is live for [Engineering / your team]

    Team,

    As of today you have access to Claude Code, an AI coding agent that runs in
    your terminal, reads your actual codebase, and works through real tasks end
    to end: debugging, refactors, tests, PRs. It is not autocomplete and it is
    not a chat window. It edits files, runs your commands, and asks permission
    before anything risky.

    Get running in two minutes:

        curl -fsSL https://claude.ai/install.sh | bash
        cd <your-repo>
        claude

    Then run /init once. Claude reads your project and writes a CLAUDE.md with
    your build commands and conventions, so you stop re-explaining the basics.

    Then try one of these on the repo you are already in:

      - "The test in [file] is flaky. Figure out why and fix it"
      - "Walk me through how [module] handles [X]"
      - "Look at my working diff and tell me what's risky before I push"

    Where your code goes: Claude Code runs in your terminal and talks directly
    to Anthropic's API, with no third-party servers in the loop. It asks before
    editing files or running commands. Under our Enterprise agreement, Anthropic
    does not use your code or prompts to train its models.
    Details: https://code.claude.com/docs/en/data-usage
             https://code.claude.com/docs/en/security

    Where to go with questions: #claude-code. [Owner name] is watching it
    this week.

    - [Name]

    P.S. Prefer your editor? There is a VS Code extension and a JetBrains
    plugin. Same agent, no terminal required.
    ```
  </Tab>

  <Tab title="Slack or Teams">
    ```markdown theme={null}
    🚀 *Claude Code is live for [team]*

    AI coding agent, runs in your terminal, reads your repo, does real work:
    bugs, refactors, tests, PRs. Asks before it touches anything.

    `curl -fsSL https://claude.ai/install.sh | bash` → `cd your-repo` → `claude`

    *First thing to try* → run `/init`, then: "the test in [file] is flaky,
    figure out why and fix it."

    🔒 Runs in your terminal, talks only to Anthropic's API. Under our
    Enterprise plan your code and prompts are not used to train models.
    Data usage → https://code.claude.com/docs/en/data-usage

    📚 Quickstart · VS Code · Free 1-hr course
       https://code.claude.com/docs/en/quickstart
       https://code.claude.com/docs/en/vs-code
       https://anthropic.skilljar.com/claude-code-in-action

    Questions → this thread. [Owner] is on point.
    ```
  </Tab>
</Tabs>

### Executive sponsor variant

Send this from your sponsoring executive, such as the CTO, CIO, or SVP Engineering, under their name and from their account. Launches that go out under an exec's name consistently see higher open rates and faster first-week activation than the same message from an admin or tooling team. It signals a company priority rather than an optional experiment.

This version is deliberately stripped to one ask: install it and run it on one real task. The exec's job is to make the ask land; the standard announcement and `#claude-code` handle the how.

<Tabs>
  <Tab title="Email">
    ```text theme={null}
    Subject: One thing I'd like every engineer to try this week

    Team,

    We have turned on Claude Code for all of engineering. It is an AI agent
    that works directly in your terminal, on your actual codebase, and the
    early results from teams already using it are strong enough that I want
    everyone on it this week.

    I am asking for ten minutes:

        curl -fsSL https://claude.ai/install.sh | bash
        cd <your-repo>
        claude

    Then hand it one real task: the bug you have been putting off, or "walk me
    through how [module] works."

    That is the whole ask. [Owner name] and team are in #claude-code for
    anything you hit along the way.

    - [Exec Name]
      [Title]
    ```
  </Tab>

  <Tab title="Slack or Teams">
    ```markdown theme={null}
    📣 *From [Exec Name]: one thing to try this week*

    We have turned on *Claude Code* for all of engineering. Early results are
    strong enough that I am asking everyone to give it ten minutes on real
    work this week.

    `curl -fsSL https://claude.ai/install.sh | bash` → `cd your-repo` →
    `claude` → hand it one real task.

    That's it. Questions → #claude-code.
    ```
  </Tab>
</Tabs>

### Pilot group variant

Use for a phased rollout. Send to the pilot cohort only.

```text theme={null}
Subject: You're in the Claude Code pilot

[Name / team],

You are in the first wave of Claude Code at [company]. We picked this group
because you will put it on real problems and tell us the truth about it.

The ask: use it on at least one real task this week, then drop a note in
#claude-code-pilot covering what worked, what was annoying, and what
surprised you. That feedback decides how we roll it out to everyone else.

[Continue with "Get running in two minutes" from the standard announcement]

One extra thing for pilots: on your first multi-file change, press Shift+Tab
until you see "plan". Claude will lay out exactly what it intends to do
before it touches a file. It is the fastest way to calibrate how much to
trust it.
```

### Champion recruitment DM

After launch, DM the two or three people who are most active in `#claude-code`.

```text theme={null}
Hey [name], your #claude-code posts are doing more for adoption than my
announcement did. A couple of people told me your [thread / screenshot]
was why they actually tried it.

Want to make that semi-official? Low lift: mostly keep posting what you
are posting, plus first crack at new features and a direct line to the
Anthropic team. I can share a short playbook if you're in.
```

## Tips and tricks campaign

Ready-to-paste Slack or Teams messages designed to drive feature activation after launch. Each follows the same pattern: a hook, the payoff, a "try it now" prompt, and a docs link. Drip them one or two a week in `#claude-code`, or pick the handful that match your team's gaps. They stand alone with no required order.

### Get started

**Choosing the right model**

```markdown theme={null}
🎯 *Tip: Match the model to the moment*

Using Opus to fix a typo burns compute. Using Haiku for a 12-file refactor
is asking for a re-do.

Claude Code runs on the same models as the Claude app, and you can switch
mid-session. *Sonnet* is the workhorse default for everyday feature work,
bugs, tests, and reviews. Reach for *Opus* on large refactors, gnarly
debugging, or anything high-stakes. Drop to *Haiku* for quick questions,
formatting, and mechanical edits where speed wins. *Fable 5* is the most
capable model for your hardest, longest-running tasks; it is not the
default, so select it with `/model fable`, and note that cybersecurity and
biology content falls back to Opus automatically. Opus 5 runs its own
checks, so flagged cybersecurity content switches models and flagged
biology content is refused.

*Try it now:* type `/model` and pick Sonnet if you haven't already. It is
the right default for most tasks.

📖 Model configuration → https://code.claude.com/docs/en/model-config
```

| Model   | Best for                                                                                                                                                                                                                       |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Fable 5 | The hardest, longest-running tasks. Opt-in only: select it with `/model fable`. Cybersecurity or biology content [falls back to Opus](/docs/en/model-config#automatic-model-fallback)                                               |
| Opus    | Large-scale refactors, complex debugging, architecture decisions, high-stakes changes. On Opus 5, cybersecurity or biology content triggers [automatic model fallback or a refusal](/docs/en/model-config#automatic-model-fallback) |
| Sonnet  | Everyday feature work, bug fixes, tests, documentation, code review. Recommended default.                                                                                                                                      |
| Haiku   | Quick questions, formatting, mechanical edits, rapid iteration                                                                                                                                                                 |

**Quick wins to try first**

```markdown theme={null}
🚀 *Tip: Three things to try in your first 10 minutes*

Installed Claude Code but not sure what to actually ask it? Start with the
stuff that has been bugging you all week.

  - Fix something annoying: "the test in [file] is flaky, figure out why"
  - Get oriented in code you didn't write: "walk me through how [module] works"
  - Sanity-check before you push: "look at my working diff and tell me what
    looks risky"

None of these need setup. Just `cd` into your repo and run `claude`.

*Try it now:* pick the bug you have been avoiding and paste the error
message in.

📖 Quickstart → https://code.claude.com/docs/en/quickstart
```

### Project memory

**`/init` and CLAUDE.md**

```markdown theme={null}
📁 *Tip: Stop re-explaining your repo every session*

Telling Claude "we use pnpm, not npm" for the fifth time? There is a
one-time fix.

Run `/init` once per repo. Claude reads your project structure and writes a
CLAUDE.md file with your build commands, architecture, and conventions.
Every future session in that repo starts from this file automatically. Keep
it under two screens. It is a cheat sheet, not documentation.

*Try it now:* open your main repo, run `claude`, type `/init`. Thirty
seconds, pays off every session after.

📖 CLAUDE.md and project memory → https://code.claude.com/docs/en/memory
```

**@-references**

```markdown theme={null}
📎 *Tip: Stop pasting file contents into the chat*

Copying 200 lines of a component into your prompt so Claude can "see" it?
You don't have to.

Type `@` then a file path. Claude pulls the file directly into context.
Works for whole directories too.

> the styles in @src/components/Button.tsx look off, check against
> @docs/design-system.md

*Try it now:* type `@` then Tab. Autocomplete shows you every file in reach.

📖 Referencing files → https://code.claude.com/docs/en/common-workflows
```

### Control and safety

**Permission modes**

```markdown theme={null}
🛡️ *Tip: One keystroke between "look but don't touch" and "just do it"*

Sometimes you want Claude to ask before every edit. Sometimes you just want
it to ship. You shouldn't have to pick one forever.

Cut at 300 lines.