11# Output styles
22
3- > [ DEPRECATED] Adapt Claude Code for uses beyond software engineering
4-
5- <Warning >
6- Output styles are ** DEPRECATED.** On ** November 5, 2025** or later, we'll
7- stop supporting the output styles feature. Use ` --system-prompt-file ` ,
8- ` --system-prompt ` , ` --append-system-prompt ` , CLAUDE.md, or [ plugins] ( /en/docs/claude-code/plugins ) instead.
9- For ** Explanatory** output style users, you can reference the ([ explanatory-output-style
10- plugin] ( https://github.com/anthropics/claude-code/tree/main/plugins/explanatory-output-style )
11- in our public repository.)
12- </Warning >
13-
14- ## Deprecation timeline
15-
16- As of ** November 5, 2025** , Claude Code will:
17-
18- * Stop supporting the output styles feature
19- * Remove the ` /output-style ` command and related functionality
20-
21- ## Alternative for Custom Output Styles
22-
23- Use ` --system-prompt-file ` to start a Claude Code session with your own system
24- prompt. You can also use ` --system-prompt ` to pass in a string to use as the system prompt, or
25- ` --append-system-prompt ` to add to the default Claude Code system prompt.
26-
27- ## Alternative for Explanatory Output Style: explanatory-output-style Plugin
28-
29- Plugins provide more powerful and flexible ways to customize Claude Code's
30- behavior. The
31- [ ` explanatory-output-style ` plugin] ( https://github.com/anthropics/claude-code/tree/main/plugins/explanatory-output-style )
32- recreates the deprecated Explanatory output style functionality.
33-
34- ### Example: Explanatory Output Style Plugin
35-
36- The ` explanatory-output-style ` plugin uses a SessionStart hook to inject
37- additional context that encourages Claude to provide educational insights.
38- Here's what it does:
39-
40- * Provides educational insights about implementation choices
41- * Explains codebase patterns and decisions
42- * Balances task completion with learning opportunities
43-
44- ### Installing a plugin
45-
46- To install a plugin like ` explanatory-output-style ` :
47-
48- ``` shell Add the marketplace (if not already added) theme={null}
49- /plugin marketplace add anthropics/claude-code
50- ```
51-
52- ``` shell Install the plugin theme={null}
53- /plugin install explanatory-output-style@claude-code-plugins
54- ```
55-
56- ``` shell Restart Claude Code to activate the plugin theme={null}
57- /exit
58- ```
59-
60- ``` shell Disable the plugin theme={null}
61- /plugin manage explanatory-output-style@claude-code-plugins
62-
63- 1. Press enter when you see claude-code-marketplace
64- 2. Press space when you see explanatory-output-style to toggle enabled
65- 3. Press down to " Apply changes" , then press enter
66- You should see " Disabled 1 plugin. Restart Claude Code to apply changes."
67-
68- /exit
69- ```
70-
71- For more details on plugins, see the
72- [ Plugins documentation] ( /en/docs/claude-code/plugins ) .
73-
74- ***
75-
76- ## Reference: Original output styles documentation
77-
78- <Note >
79- The content below is preserved for reference only. Output styles are
80- deprecated and will be removed on November 5, 2025. Please migrate to plugins,
81- hooks, or subagents.
82- </Note >
3+ > Adapt Claude Code for uses beyond software engineering
834
845Output styles allow you to use Claude Code as any type of agent while keeping
856its core capabilities, such as running local scripts, reading/writing files, and
867tracking TODOs.
878
88- ### Built-in output styles
9+ ## Built-in output styles
8910
9011Claude Code's ** Default** output style is the existing system prompt, designed
9112to help you complete software engineering tasks efficiently.
@@ -102,7 +23,7 @@ codebase and how Claude operates:
10223 pieces of code yourself. Claude Code will add ` TODO(human) ` markers in your
10324 code for you to implement.
10425
105- ### How output styles work
26+ ## How output styles work
10627
10728Output styles directly modify Claude Code's system prompt.
10829
@@ -112,7 +33,7 @@ Output styles directly modify Claude Code's system prompt.
11233* Instead, these output styles have their own custom instructions added to the
11334 system prompt.
11435
115- ### Change your output style
36+ ## Change your output style
11637
11738You can either:
11839
@@ -125,36 +46,54 @@ You can either:
12546These changes apply to the [ local project level] ( /en/docs/claude-code/settings )
12647and are saved in ` .claude/settings.local.json ` .
12748
128- You can also create your own output style Markdown files and save them either at
129- the user level (` ~/.claude/output-styles ` ) or the project level
130- (` .claude/output-styles ` ).
49+ ## Create a custom output style
13150
132- ### Comparisons to related features
51+ To set up a new output style with Claude's help, run
52+ ` /output-style:new I want an output style that ... `
13353
134- #### Output Styles vs. CLAUDE.md vs. System Prompt Flags
54+ By default, output styles created through ` /output-style:new ` are saved as
55+ markdown files at the user level in ` ~/.claude/output-styles ` and can be used
56+ across projects. They have the following structure:
13557
136- Output styles completely "turn off" the parts of Claude Code's default system
137- prompt specific to software engineering.
58+ ``` markdown theme={null}
59+ ---
60+ name: My Custom Style
61+ description:
62+ A brief description of what this style does, to be displayed to the user
63+ ---
64+
65+ # Custom Style Instructions
66+
67+ You are an interactive CLI tool that helps users with software engineering
68+ tasks. [ Your custom instructions here...]
69+
70+ ## Specific Behaviors
71+
72+ [ Define how the assistant should behave in this style...]
73+ ```
13874
139- ** CLAUDE.md** adds the contents as a user message * following* Claude Code's default system
140- prompt, rather than modifying the system prompt itself.
75+ You can also create your own output style Markdown files and save them either at
76+ the user level (` ~/.claude/output-styles ` ) or the project level
77+ (` .claude/output-styles ` ).
14178
142- ** System prompt CLI flags ** provide different levels of control:
79+ ## Comparisons to related features
14380
144- * ` --append-system-prompt ` : Appends text to the end of the default system prompt
145- * ` --system-prompt ` : Replaces the entire default system prompt with custom text
146- * ` --system-prompt-file ` : Loads a custom system prompt from a file
81+ ### Output Styles vs. CLAUDE.md vs. --append-system-prompt
14782
148- See the [ CLI reference] ( /en/docs/claude-code/cli-reference#system-prompt-flags ) for detailed guidance on when to use each flag.
83+ Output styles completely "turn off" the parts of Claude Code's default system
84+ prompt specific to software engineering. Neither CLAUDE.md nor
85+ ` --append-system-prompt ` edit Claude Code's default system prompt. CLAUDE.md
86+ adds the contents as a user message * following* Claude Code's default system
87+ prompt. ` --append-system-prompt ` appends the content to the system prompt.
14988
150- #### Output Styles vs. [ Agents] ( /en/docs/claude-code/sub-agents )
89+ ### Output Styles vs. [ Agents] ( /en/docs/claude-code/sub-agents )
15190
15291Output styles directly affect the main agent loop and only affect the system
15392prompt. Agents are invoked to handle specific tasks and can include additional
15493settings like the model to use, the tools they have available, and some context
15594about when to use the agent.
15695
157- #### Output Styles vs. [ Custom Slash Commands] ( /en/docs/claude-code/slash-commands )
96+ ### Output Styles vs. [ Custom Slash Commands] ( /en/docs/claude-code/slash-commands )
15897
159- You can think of output styles as “ stored system prompts” and custom slash
160- commands as “ stored prompts” .
98+ You can think of output styles as " stored system prompts" and custom slash
99+ commands as " stored prompts" .
0 commit comments