2026年5月14日 06:31

4 ファイル変更+65-92

この更新の概要

Claude Codeの各機能が利用可能なプラン構成と、APIプロバイダーごとの制限事項が明確化されました。カスタム出力スタイルにおいて、組み込みのソフトウェアエンジニアリング指示を維持するかを選択できるkeep-coding-instructionsオプションが導入されています。プロジェクト固有の指示ファイルであるCLAUDE.mdの読み込み優先順位が整理され、ユーザー設定との競合が解消されました。各カスタマイズ機能の比較表が拡充され、出力スタイル、CLAUDE.md、エージェントなどの使い分けがより具体的に解説されています。

admin-setup+3-1

RoutinesやCode Reviewなどの高度な機能にはClaude.aiアカウントが必要であることを明記し、APIプロバイダー経由の利用における制限事項が追加されました。

@@ -23,7 +23,7 @@ SSO, SCIM provisioning, and seat assignment are configured at the Claude account

## Choose your API provider

Claude Code connects to Claude through one of several API providers. Your choice affects billing, authentication, and which compliance posture you inherit.

Claude Code connects to Claude through one of several API providers. Your choice affects billing, authentication, which compliance posture you inherit, and which Claude Code features your developers can use.

| Provider | Choose this when |

| :- | :- |

@@ -33,6 +33,8 @@ Claude Code connects to Claude through one of several API providers. Your choice

| Google Vertex AI | You want to inherit existing GCP compliance controls and billing |

| Microsoft Foundry | You want to inherit existing Azure compliance controls and billing |

Some Claude Code features require a Claude.ai account. [Claude Code on the web](/en/claude-code-on-the-web), [Routines](/en/routines), [Code Review](/en/code-review), [Remote Control](/en/remote-control), and the [Chrome extension](/en/chrome) are not available through Console API keys or cloud-provider credentials alone. If you deploy through Bedrock, Vertex, or Foundry, plan whether developers also need Claude for Teams or Enterprise seats. Each feature page lists its plan requirements.

For the full provider comparison covering authentication, regions, and feature parity, see the [enterprise deployment overview](/en/third-party-integrations). Each provider's auth setup is in [Authentication](/en/authentication).

Proxy and firewall requirements in [Network configuration](/en/network-config) apply regardless of provider. If you want a single endpoint in front of multiple providers or centralized request logging, see [LLM gateway](/en/llm-gateway).

agent-sdk/modifying-system-prompts+6-3

カスタムプロンプト作成時にデフォルトのコーディング指示を継承するためのkeep-coding-instructions設定と、その具体的な活用例が追記されました。

@@ -107,14 +107,17 @@ Output styles are saved configurations that modify Claude's system prompt. They'

#### Create an output style

An output style is a markdown file with a `name` and `description` in its frontmatter, followed by the prompt content. Save it to `~/.claude/output-styles/` for a user-level style available in every project, or `.claude/output-styles/` in your repository for a project-level style you can commit and share with your team.

An output style is a markdown file with [frontmatter](/en/output-styles#frontmatter) for metadata, followed by the prompt content. Save it to `~/.claude/output-styles/` for a user-level style available in every project, or `.claude/output-styles/` in your repository for a project-level style you can commit and share with your team.

The example below defines a code-review persona. Save it as `~/.claude/output-styles/code-reviewer.md` to make it available across projects:

By default, a custom output style replaces the `claude_code` preset's software engineering instructions with your own. To keep them and layer your instructions on top, set `keep-coding-instructions: true` in the frontmatter. Keep them when your agent is still doing software engineering work. Leave them out when you're replacing the role entirely.

The example below defines a code-review persona that keeps the coding instructions, since reviewing code still benefits from Claude Code's security and code-quality guidance. Save it as `~/.claude/output-styles/code-reviewer.md` to make it available across projects:

```markdown ~/.claude/output-styles/code-reviewer.md theme={null}

---

description: Thorough code review assistant

keep-coding-instructions: true

---

You are an expert code reviewer.

@@ -297,7 +300,7 @@ The four customization methods differ in where they live, how they're shared, an

memory+2-2

CLAUDE.mdファイルの読み込み順序が整理され、プロジェクト固有の指示がユーザーレベルの指示よりも後に読み込まれ優先される仕組みが説明されています。

@@ -52,13 +52,13 @@ Keep it to facts Claude should hold in every session: build commands, convention

### Choose where to put CLAUDE.md files

CLAUDE.md files can live in several locations, each with a different scope. More specific locations take precedence over broader ones.

CLAUDE.md files can live in several locations, each with a different scope. The table below lists them in load order, from broadest scope to most specific, so a project instruction appears in context after a user instruction.

| - | - | - | - | - |

| **Managed policy** | • macOS: `/Library/Application Support/ClaudeCode/CLAUDE.md`• Linux and WSL: `/etc/claude-code/CLAUDE.md`• Windows: `C:\Program Files\ClaudeCode\CLAUDE.md` | Organization-wide instructions managed by IT/DevOps | Company coding standards, security policies, compliance requirements | All users in organization |

CLAUDE.md and CLAUDE.local.md files in the directory hierarchy above the working directory are loaded in full at launch. Files in subdirectories load on demand when Claude reads files in those directories. See [How CLAUDE.md files load](#how-claude-md-files-load) for the full resolution order.

output-styles+54-86

出力スタイルの設定方法が刷新され、他のカスタマイズ機能との機能比較表や、より実践的なMermaidダイアグラム出力のテンプレート例が掲載されました。

@@ -7,59 +7,29 @@ source: https://code.claude.com/docs/en/output-styles.md

> Adapt Claude Code for uses beyond software engineering

Output styles change how Claude responds, not what Claude knows. They modify the system prompt to set role, tone, and output format while keeping core capabilities like running scripts, reading and writing files, and tracking TODOs. Use one when you keep re-prompting for the same voice or format every turn, or when you want Claude to act as something other than a software engineer.

Output styles change how Claude responds, not what Claude knows. They modify the system prompt to set role, tone, and output format. Use one when you keep re-prompting for the same voice or format every turn, or when you want Claude to act as something other than a software engineer.

A custom output style adds your instructions to the system prompt and lets you choose whether to keep Claude Code's built-in software engineering instructions. Keep them when you're changing how Claude communicates but still coding, like always answering with a diagram. Leave them out when Claude isn't doing software engineering at all, like a writing assistant or data analyst.

For instructions about your project, conventions, or codebase, use [CLAUDE.md](/en/memory) instead.

## Built-in output styles

Claude Code's **Default** output style is the existing system prompt, designed

to help you complete software engineering tasks efficiently.

Claude Code's **Default** output style is the existing system prompt, designed to help you complete software engineering tasks efficiently.

There are three additional built-in output styles:

- **Proactive**: Claude executes immediately, makes reasonable assumptions

instead of pausing for routine decisions, and prefers action over planning.

This applies the same guidance as

[auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode) without

changing your permission mode, so you still see permission prompts before

tools run.

- **Explanatory**: Provides educational "Insights" in between helping you

complete software engineering tasks. Helps you understand implementation

choices and codebase patterns.

- **Learning**: Collaborative, learn-by-doing mode where Claude will not only

share "Insights" while coding, but also ask you to contribute small, strategic

pieces of code yourself. Claude Code will add `TODO(human)` markers in your

code for you to implement.

## How output styles work

Output styles directly modify Claude Code's system prompt.

- **Proactive**: Claude executes immediately, makes reasonable assumptions instead of pausing for routine decisions, and prefers action over planning. This applies the same guidance as [auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode) without changing your permission mode, so you still see permission prompts before tools run.

- Custom output styles exclude instructions for coding (such as verifying code

with tests), unless `keep-coding-instructions` is true.

- All output styles have their own custom instructions added to the end of the

system prompt.

- All output styles trigger reminders for Claude to adhere to the output style

instructions during the conversation.

- **Explanatory**: Provides educational "Insights" in between helping you complete software engineering tasks. Helps you understand implementation choices and codebase patterns.

Token usage depends on the style. Adding instructions to the system prompt

increases input tokens, though prompt caching reduces this cost after the first

request in a session. The built-in Explanatory and Learning styles produce

longer responses than Default by design, which increases output tokens. For

custom styles, output token usage depends on what your instructions tell Claude

to produce.

- **Learning**: Collaborative, learn-by-doing mode where Claude will not only share "Insights" while coding, but also ask you to contribute small, strategic pieces of code yourself. Claude Code will add `TODO(human)` markers in your code for you to implement.

## Change your output style

Run `/config` and select **Output style** to pick a style from a menu. Your

selection is saved to `.claude/settings.local.json` at the

[local project level](/en/settings).

Run `/config` and select **Output style** to pick a style from a menu. Your selection is saved to `.claude/settings.local.json` at the [local project level](/en/settings).

To set a style without the menu, edit the `outputStyle` field directly in a

settings file:

To set a style without the menu, edit the `outputStyle` field directly in a settings file:

```json

{

@@ -67,78 +37,76 @@ settings file:

}

```

Because the output style is set in the system prompt at session start,

changes take effect the next time you start a new session. This keeps the system

prompt stable throughout a conversation so prompt caching can reduce latency and

cost.

Because the output style is set in the system prompt at session start, changes take effect the next time you start a new session. This keeps the system prompt stable throughout a conversation so prompt caching can reduce latency and cost.

## Create a custom output style

Custom output styles are Markdown files with frontmatter and the text that will

be added to the system prompt:

A custom output style is a Markdown file: frontmatter for metadata, then the instructions to add to the system prompt.

Save it at one of three levels. The file name becomes the style name unless you set `name` in the frontmatter.

- User: `~/.claude/output-styles`

- Project: `.claude/output-styles`

- Managed policy: `.claude/output-styles` inside the [managed settings directory](/en/settings#settings-files)

Decide whether to keep Claude Code's software engineering instructions. Set `keep-coding-instructions: true` if you're changing how Claude communicates but still want it coding the same way. Leave it out if Claude won't be doing software engineering.

```markdown

This example leads every explanation with a diagram while keeping Claude's coding behavior:

```markdown theme={null}

---

description:

A brief description of what this style does, to be displayed to the user

description: Lead every explanation with a diagram

keep-coding-instructions: true

---

# Custom Style Instructions

You are an interactive CLI tool that helps users with software engineering

tasks. [Your custom instructions here...]

When explaining code, architecture, or data flow, start with a Mermaid diagram showing the structure, then explain in prose.

## Specific Behaviors

## Diagram conventions

[Define how the assistant should behave in this style...]

Use `flowchart TD` for control flow and `sequenceDiagram` for request paths. Keep diagrams under 15 nodes.

```

You can save these files at three levels:

- User: `~/.claude/output-styles`

- Project: `.claude/output-styles`

- Managed policy: `.claude/output-styles` inside the [managed settings directory](/en/settings#settings-files)

Run `/config` and select your style under **Output style**. It takes effect the next time you start a session.

[Plugins](/en/plugins-reference) can also ship output styles in an `output-styles/` directory.

### Frontmatter

Output style files support frontmatter for specifying metadata:

Output style files support these frontmatter fields:

| Frontmatter | Purpose | Default |

| :- | :- | :- |

| `name` | Name of the output style, if not the file name | Inherits from file name |

| `description` | Description of the output style, shown in the `/config` picker | None |

| `keep-coding-instructions` | Whether to keep the parts of Claude Code's system prompt related to coding. | false |

| `force-for-plugin` | Plugin output styles only: apply this style automatically whenever the plugin is enabled, without requiring users to select it. Overrides the user's `outputStyle` setting. If multiple enabled plugins set this, the first one loaded wins. | false |

| `keep-coding-instructions` | Keep Claude Code's built-in software engineering instructions | `false` |

## Comparisons to related features

### Output Styles vs. CLAUDE.md vs. --append-system-prompt

## How output styles work

Choose based on whether Claude should stop acting as a coding assistant or keep

its default role and learn more. Output styles replace the software-engineering

parts of Claude Code's system prompt with your own role and voice, so use one

when Claude should adopt a different identity, like a writing editor or a

data-analysis assistant. CLAUDE.md and `--append-system-prompt` both keep

Claude Code's default identity and add to it, so use them when Claude should

remain a coding assistant that also follows your project conventions or extra

instructions.

Output styles directly modify Claude Code's system prompt.

The mechanisms differ as well. Output styles edit the system prompt directly.

CLAUDE.md adds its contents as a user message after the system prompt.

`--append-system-prompt` appends content to the end of the system prompt without

removing anything.

- All output styles have their own custom instructions added to the end of the system prompt.

- All output styles trigger reminders for Claude to adhere to the output style instructions during the conversation.

- Custom output styles leave out Claude Code's built-in software engineering instructions, such as how to scope changes, write comments, and verify work, unless `keep-coding-instructions` is set to `true`.

### Output Styles vs. [Agents](/en/sub-agents)

Token usage depends on the style. Adding instructions to the system prompt increases input tokens, though prompt caching reduces this cost after the first request in a session. The built-in Explanatory and Learning styles produce longer responses than Default by design, which increases output tokens. For custom styles, output token usage depends on what your instructions tell Claude to produce.

Use an output style to change how the main conversation responds in every

session. Use a [subagent](/en/sub-agents) when you want a separately scoped

helper that the main conversation delegates to. Output styles affect only the

system prompt of the main agent loop. Agents handle specific tasks and can carry

their own model, tools, and context about when to invoke them.

## Comparisons to related features

### Output Styles vs. [Skills](/en/skills)

Several features customize how Claude Code behaves. Output styles modify the system prompt directly and apply to every response. The others add instructions without changing the default system prompt, or scope them to a specific task.

Output styles modify how Claude responds (formatting, tone, structure) and are always active once selected. Skills are task-specific prompts that you invoke with `/skill-name` or that Claude loads automatically when relevant. Use output styles for consistent formatting preferences; use skills for reusable workflows and tasks.

| Feature | How it works | Use it when |

| :- | :- | :- |

| Output styles | Modifies the system prompt | You want a different role, tone, or default response format every turn |

| [CLAUDE.md](/en/memory) | Adds a user message after the system prompt | Claude should always know your project conventions and codebase context |

| `--append-system-prompt` | Appends to the system prompt without removing anything | You want a one-off addition for a single invocation |

| [Agents](/en/sub-agents) | Runs a subagent with its own system prompt, model, and tools | You want a separately scoped helper for a focused task |

| [Skills](/en/skills) | Loads task-specific instructions when invoked or relevant | You have a reusable workflow |

## Related resources

- [Settings](/en/settings): where the `outputStyle` field lives and how settings precedence works

- [Permission modes](/en/permission-modes): the Proactive style mirrors auto mode without changing your permission mode

- [Plugins](/en/plugins): package and distribute output styles alongside skills, hooks, and agents

- [Debug your configuration](/en/debug-your-config): diagnose why an output style isn't taking effect