claude-output-styles
Claude Code Output Styles
Guide for the native Claude Code output style feature and for applying the same response-contract pattern to agents, slash commands, teams, and skills.
When to Use This Skill
Activate this skill when:
- Creating a custom output style for a session or plugin
- Shipping output styles from a plugin via the
output-styles/directory - Deciding whether a need is best served by an output style, a skill, CLAUDE.md, or
--append-system-prompt - Standardizing the response shape a worker agent must return so a team lead can filter and parse it
- Writing reusable response-format contracts that multiple agents, commands, or skills reference
- Debugging why a subagent is not honoring the session's output style
Two Things This Skill Covers
- The Claude Code feature: a session-level system prompt modification selected via
/config, shipped as Markdown files, optionally bundled in plugins. - The pattern: a reusable response-format contract authored once and referenced from agents, commands, teams, or skills when consistent, parseable output is needed.
More from vinnie357/claude-skills
material-design
Guide for implementing Material Design 3 (Material You). Use when designing Android apps, implementing dynamic theming, or following Material component patterns.
18elixir-testing
Guide for Elixir testing with ExUnit. Use when writing unit tests, implementing property-based tests, setting up mocks, or organizing test suites.
16phoenix-framework
Guide for Phoenix web applications. Use when building Phoenix apps, implementing LiveView, designing contexts, setting up channels, or integrating Tidewave MCP dev tools.
16elixir-anti-patterns
Identify and refactor Elixir anti-patterns. Use when reviewing Elixir code for smells, refactoring problematic patterns, or improving code quality.
15nushell
Guide for using Nushell for structured data pipelines and scripting. Use when writing shell scripts, processing structured data, or working with cross-platform automation.
14documentation-writing
Guide for writing technical documentation. Use when creating README files, API documentation, guides, or inline code documentation.
12