generating-output-styles

Generate Claude Code output style files with YAML frontmatter.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/Emz1998/avaris-ai --skill generating-output-styles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-output-styles
Source: https://github.com/Emz1998/avaris-ai/tree/main/.claude/skills/output-style
Command: npx skills add https://github.com/Emz1998/avaris-ai --skill generating-output-styles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Output styles allow Claude Code to be customized for non-software-engineering tasks by changing system prompts.

Core Features & Use Cases

  • Define new output styles: Markdown files with frontmatter that modify Claude Code's prompting.
  • Placement: Choose user-level or project-level directories.
  • Testing: Use /output-style to activate and verify in menu.
  • Use Case: Quickly tailor Claude Code responses for non-engineering tasks like writing, teaching, or brainstorming.

Quick Start

Create a new style in .claude/output-styles/ or ~/.claude/output-styles/, then run /output-style to activate.

Frequently Asked Questions about generating-output-styles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize Claude Code's response format for non-engineering tasks?

Output styles let you customize Claude Code's system prompt via markdown files with YAML frontmatter. Create a file in `.claude/output-styles/` or `~/.claude/output-styles/`, then activate it with `/output-style` to tailor responses for writing, teaching, or brainstorming tasks.

What's the correct structure for an output style file?

Output style files use YAML frontmatter to define metadata like name and description, followed by the custom system prompt content. Valid frontmatter must include proper naming constraints, keep-coding-instructions flags, and be placed in the correct directory for project or user-level activation.

Can I use output styles at both project and user levels?

Yes, output styles support both placement options: `.claude/output-styles/` for project-specific styles and `~/.claude/output-styles/` for user-level styles. Project-level styles override user-level ones when both exist in the same workflow.

How do I test and activate a custom output style?

After creating your output style file with proper frontmatter and naming conventions, run the `/output-style` command in Claude Code to view available styles and activate your custom one. This lets you verify the style works before using it in tasks.

What constraints apply when creating output style files?

Output style files must have valid YAML frontmatter, follow naming and description constraints, include appropriate keep-coding-instructions flags, and be placed in `.claude/output-styles/` or `~/.claude/output-styles/`. Invalid frontmatter or placement will prevent activation.

Can output styles modify how Claude Code handles non-software-engineering work?

Yes, output styles are designed specifically to customize Claude Code for non-engineering tasks by changing system prompts. This allows you to adjust response format, tone, and behavior for writing, teaching, analysis, and other non-code workflows.