[DOCS] Plugin output styles docs omit `keep-coding-instructions` frontmatter support

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/output-styles

Section/Topic

Create a custom output style / Frontmatter, plus the plugin outputStyles reference

Current Documentation

The docs currently say:

Custom output styles are Markdown files with frontmatter and the text that will be added to the system prompt: You can save these files at the user level (~/.claude/output-styles) or project level (.claude/output-styles). | keep-coding-instructions | Whether to keep the parts of Claude Code's system prompt related to coding. | false |

And the plugin reference separately says:

| outputStyles | string\|array | Custom output style files/directories (replaces default output-styles/) | "./styles/" |

What's Wrong or Missing?

Changelog v2.1.94 added keep-coding-instructions frontmatter field support for plugin output styles, but the docs never connect that behavior to plugin-authored output styles.

A. Output style authoring docs only describe user/project files

The output styles page documents the keep-coding-instructions field, but it only says output style files live in ~/.claude/output-styles or .claude/output-styles. It does not say that the same frontmatter also applies when the file is shipped from a plugin.

B. Plugin docs expose the directory, but not the frontmatter contract

plugins-reference documents the outputStyles manifest field and output-styles/ directory, but it does not say that plugin-shipped output styles use the same markdown/frontmatter schema as standalone output styles, or that keep-coding-instructions: true is supported there.

As written, a plugin author can discover that plugins may ship output styles, and can separately discover that keep-coding-instructions exists, but cannot confirm from the docs that the field works for plugin output styles.

Suggested Improvement

Update the output style and plugin docs together:

1. On https://code.claude.com/docs/en/output-styles, expand the file-location guidance to include plugin-shipped output styles and explicitly say plugin output style files use the same frontmatter fields.
2. On https://code.claude.com/docs/en/plugins-reference, add a short cross-reference from outputStyles / output-styles/ to the output styles page, plus a minimal example such as:

---
description: Keep the default coding workflow and add review notes
keep-coding-instructions: true
---

Add a short rationale after each code change.

1. Mention that this behavior is available as of changelog v2.1.94.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/output-styles | Documents output style frontmatter, including keep-coding-instructions, but only lists user/project file locations |
| https://code.claude.com/docs/en/plugins-reference | Documents plugin outputStyles paths and output-styles/ directories, but not the frontmatter fields supported by those files |

Total scope: 2 pages affected

Source: Changelog v2.1.94

Exact changelog entry: Added \keep-coding-instructions\ frontmatter field support for plugin output styles