### Update documentation prompt example

Source: https://code.claude.com/docs/en/quickstart

Prompt example asking Claude to update README installation instructions.

```text
update the README with installation instructions

```

--------------------------------

### Start guided runner setup with claude self-hosted-runner setup

Source: https://code.claude.com/docs/en/self-hosted-environments-quickstart

Starts an interactive guided Claude Code session that walks through creating an environment and configuring a local runner. Requires signing in with an Owner role account and Claude Code version 2.1.224 or later.

```bash
claude self-hosted-runner setup

```

--------------------------------

### Install httpx using uv

Source: https://code.claude.com/docs/en/agent-sdk/custom-tools

Installs the httpx dependency for making HTTP requests in Python examples using uv.

```bash
uv add httpx

```

--------------------------------

### Run installation and configuration diagnostics

Source: https://code.claude.com/docs/en/setup

Prints read-only installation and settings diagnostics without starting a session. Displays install health, settings-file validation errors, and warnings with suggested fixes.

```bash
claude doctor

```

--------------------------------

### Generate teammate ramp-up guide with /team-onboarding

Source: https://code.claude.com/docs/en/whats-new/2026-w15

Creates a project-specific ramp-up guide based on local Claude Code usage to share custom setup with new teammates.

```text
/team-onboarding

```

--------------------------------

### Install httpx using pip

Source: https://code.claude.com/docs/en/agent-sdk/custom-tools

Installs the httpx dependency for making HTTP requests in Python examples using pip.

```bash
pip install httpx

```

--------------------------------

### Initialize project directory and install dependencies

Source: https://code.claude.com/docs/en/channels-reference

Create a new project directory and install the Model Context Protocol SDK along with Zod using Bun.

```bash
mkdir webhook-channel && cd webhook-channel
bun add @modelcontextprotocol/sdk zod

```

--------------------------------

### Set up the marketplace directory and copy plugin

Source: https://code.claude.com/docs/en/plugins/create-marketplace

Creates the marketplace folder structure including the .claude-plugin/ metadata directory and copies your plugin into the plugins/ subfolder.

```bash
mkdir -p my-marketplace/.claude-plugin my-marketplace/plugins
cp -r my-first-plugin my-marketplace/plugins/

```

--------------------------------

### Run plugin install command syntax

Source: https://code.claude.com/docs/en/plugins/cli-reference

Basic command syntax to install a plugin from configured marketplaces.

```bash
claude plugin install <plugin> [options]

```

--------------------------------

### Install plugin from the registered marketplace

Source: https://code.claude.com/docs/en/plugins/create-marketplace

Installs the plugin using the format <plugin-name>@<marketplace-name> at user scope.

```bash
claude plugin install my-first-plugin@my-marketplace

```

--------------------------------

### Install @anthropic-ai/sandbox-runtime

Source: https://code.claude.com/docs/en/agent-sdk/secure-deployment

Installs the sandbox-runtime package for lightweight OS-level filesystem and network isolation without requiring Docker or container setups.

```bash
npm install @anthropic-ai/sandbox-runtime

```

--------------------------------

### Install a plugin using claude plugin install with project scope

Source: https://code.claude.com/docs/en/plugins/install

Installs a plugin directly from the shell without starting an interactive session. Set the scope to project level using `--scope project`.

```bash
claude plugin install formatter@your-org --scope project

```

--------------------------------

### Share /init and CLAUDE.md project memory tip template

Source: https://code.claude.com/docs/en/communications-kit

Share this communication template to teach developers how to initialize persistent repo context and conventions using /init and CLAUDE.md.

```markdown
📁 *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

```

--------------------------------

### Linux Out-of-Memory (OOM) Killed install error

Source: https://code.claude.com/docs/en/troubleshoot-install

Example terminal output when the Linux OOM killer terminates the installer due to insufficient free memory.

```text
Setting up Claude Code...
bash: line 183: 34803 Killed    "$binary_path" install ${TARGET:+"$TARGET"}
Installation was killed before it could finish (exit code 137). This usually means the system ran out of memory.
Claude Code needs roughly 512MB of free memory to install. Free up memory, then run this script again.

```

--------------------------------

### Create install directory and update ownership

Source: https://code.claude.com/docs/en/troubleshoot-install

Creates `~/.local/bin` and updates ownership of `~/.local` recursively to the current user if permissions are missing.

```bash
sudo mkdir -p ~/.local/bin
sudo chown -R $(whoami) ~/.local

```

--------------------------------

### Install marketplaces and plugins into a seed directory at build time

Source: https://code.claude.com/docs/en/plugins/org

Sets `CLAUDE_CODE_PLUGIN_CACHE_DIR` to the seed path so that marketplaces and plugins install into the target seed directory instead of `~/.claude/plugins`. Used during container build time or CI runner setup when runtime git cloning is unavailable.

```bash
CLAUDE_CODE_PLUGIN_CACHE_DIR=/opt/claude-seed claude plugin marketplace add your-org/your-marketplace
CLAUDE_CODE_PLUGIN_CACHE_DIR=/opt/claude-seed claude plugin install code-formatter@your-marketplace

```

--------------------------------

### Shared library error for Linux musl/glibc binary mismatch

Source: https://code.claude.com/docs/en/troubleshoot-install

An example error displayed when Claude Code installer misdetects the system's C standard library and downloads the wrong binary variant.

```text
Error loading shared library libstdc++.so.6: No such file or directory

```

--------------------------------

### Initialize and install Agent SDK with uv in Python

Source: https://code.claude.com/docs/en/agent-sdk/quickstart

Initializes a new Python project and installs the claude-agent-sdk package using the uv package manager.

```bash
uv init
uv add claude-agent-sdk
```

--------------------------------

### Run setup checkup using /doctor

Source: https://code.claude.com/docs/en/whats-new/2026-w28

Runs a diagnostic checkup on the Claude Code installation, skills, MCP servers, CLAUDE.md configuration, and hooks. Reports findings and prompts for confirmation before applying any fixes.

```shell
> /doctor

```

--------------------------------

### Install a plugin with /plugin install

Source: https://code.claude.com/docs/en/plugins/install

Opens the plugin details panel within a Claude Code session to review capabilities and choose an install scope. Replace the plugin name and marketplace as needed.

```shell
/plugin install commit-commands@claude-plugins-official

```

--------------------------------

### Register marketplace and force-enable plugins in managed settings

Source: https://code.claude.com/docs/en/plugins/org

Registers an organization marketplace under `extraKnownMarketplaces` and force-enables specified plugins. Plugins are installed at the start of the next session, and managed settings take precedence over user scopes.

```json
{
  "extraKnownMarketplaces": {
    "your-marketplace": {
      "source": { "source": "github", "repo": "your-org/your-marketplace" },
      "autoUpdate": true
    }
  },
  "enabledPlugins": {
    "code-formatter@your-marketplace": true,
    "deploy-helper@your-marketplace": true
  }
}

```

--------------------------------

### Set up the gallery mod files

Source: https://code.claude.com/docs/en/plugins/mods/gallery

Creates the mod manifest, hooks configuration, and entry point script that registers the /gallery command and renders elements in a pane.

```json
{
  "name": "gallery",
  "version": "0.1.0",
  "description": "Opens a pane that draws one sample",
  "author": { "name": "Your Name" }
}

```

```json
{
  "modules": ["./register.js"]
}

```

```javascript
// Stands in for your own callback in the samples that take one
const noop = () => {}
// The Select sample keeps its choice here
let picked = 'md'

// The Raster sample packs its cells with this function
const DEFAULT_COLOR = 0x01000000
function cellsOf(rows) {
  const numbers = rows.flat().flatMap(([char, color]) => [char.codePointAt(0), color, DEFAULT_COLOR])
  return new Uint8Array(Uint32Array.from(numbers).buffer).toBase64()
}

export function register(on) {
  on('session.start', async ($, e, next) => {
    await $.command.register({ name: 'gallery', description: 'Open the sample pane' })
    return next(e)
  })

  on('command.run', { command: 'gallery' }, async ($) => {
    await $.ui.open({ id: 'gallery', focus: true, closeOnEscape: true })
    return {}
  })

  on('ui.render', { component: 'Pane' }, async ($, e, next) => {
    if (e.requestId !== 'gallery') return next(e)
    const { Box, Text, Button, Input, Select, Link, Markdown, Code, Raster, Svg } = $.ui.resolve(e)
    // Replace the element after return with a sample
    return Text({ children: ['Plain text'] })
  })
}

```

--------------------------------

### Configure SubagentStart and SubagentStop hooks in settings.json

Source: https://code.claude.com/docs/en/sub-agents

Define session-level hooks targeting subagent lifecycle events in settings.json. Runs setup scripts when specific named subagents start and cleanup scripts when any subagent finishes.

```json
{
  "hooks": {
    "SubagentStart": [
      {
        "matcher": "db-agent",
        "hooks": [
          { "type": "command", "command": "./scripts/setup-db-connection.sh" }
        ]
      }
    ],
    "SubagentStop": [
      {
        "hooks": [
          { "type": "command", "command": "./scripts/cleanup-db-connection.sh" }
        ]
      }
    ]
  }
}

```