Skip to content
Back to search

awesome-claude-code-output-styles-that-i-really-like

A curated collection of probably the most awesome feature of Claude Code - Output Styles

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hesreallyhim-awesome-claude-code-output-styles-that-i-really-like/badge.svg)](/listings/hesreallyhim-awesome-claude-code-output-styles-that-i-really-like)

HTML

<a href="/listings/hesreallyhim-awesome-claude-code-output-styles-that-i-really-like"><img src="/api/listings/hesreallyhim-awesome-claude-code-output-styles-that-i-really-like/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 396 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <img src="resources/banners/header.svg" alt="Awesome Claude Code OUTPUT STYLES" />
  3. </p>
  4. Claude Code is a revolutionary in-your-editor and in-your-face coding agent created by Anthropic© PBC. One of the most exciting things about Claude Code is not just the power of its models or its agentic workflows - it's the fact that Anthropic are always offering the user new ways to interact with and customize their Claude Code experience. One of the best examples of this is [**Output styles**](https://code.claude.com/docs/en/output-styles).
  5. ## What Are Output Styles
  6. Output styles are a way of _overriding Claude Code's default system prompt_. Like any typical AI assistant, Claude Code has a "built-in" system prompt that instructs it in how to respond to the user. Since Claude Code is an agent that is layered on top of one or more Claude AI models, it is guided by (a) the system prompt for the Claude model (which are published on Anthropic's [website](https://platform.claude.com/docs/en/release-notes/system-prompts)) - think, "Claude is a helpful assistant..." - and (b) a special system prompt that guides Claude Code's behavior as a _coding agent_ (not published).
  7. Per the [documentation page](https://code.claude.com/docs/en/output-styles) for Claude Code:
  8. - Output styles completely “turn off” the parts of Claude Code’s default system prompt specific to software engineering.
  9. Take a moment to read that again, because it's pretty interesting - a coding agent that lets you override its instructions about coding?! OK, that's pretty cool. Maybe I didn't explain it very well, so let's give Claude Code a chance to speak for itself.
  10. **Prompt:**
  11. <pre>Can you print a clear and concise (about one paragraph) explanation to users of Claude Code
  12. about Output Styles and how to use them? Just print the explainer, no additional commentary necessary.</pre>
  13. 1. **DEFAULT OUTPUT STYLE**
  14. <pre>Output styles control how Claude Code formats and presents its responses in
  15. the terminal. You can switch between different visual styles using the
  16. /`output-style` command followed by the style name (e.g., `/output-style
  17. minimal` for clean, distraction-free output or `/output-style detailed` for
  18. comprehensive information with progress indicators). Each style is optimized
  19. for different workflows - from focused coding sessions that need minimal
  20. visual noise to detailed debugging that benefits from rich formatting and
  21. status updates. You can view available styles and their descriptions with
  22. `/output-style list`, and the setting persists across sessions until you
  23. change it again.</pre>
  24. 2. **CLAUDE CODE TECHNICAL EVANGELIST**
  25. <pre>
  26. Output Styles are a powerful feature in Claude Code that transform how the AI
  27. assistant responds to your requests while retaining all core capabilities like
  28. file manipulation, script execution, and task tracking. Think of them as
  29. specialized personas or modes that reshape Claude's communication style,
  30. expertise focus, and problem-solving approach to match your specific needs.
  31. You can activate an output style using the /output-style command followed by
  32. the style name (e.g., /output-style technical-evangelist), instantly switching
  33. Claude into that specialized mode. Whether you need a meticulous code
  34. reviewer, a creative problem solver, a documentation expert, or any other
  35. specialized assistant, output styles adapt Claude's responses to your
  36. workflow. The beauty is that you're not limited to pre-built styles – you can
  37. create custom output styles tailored to your exact requirements, essentially
  38. designing your ideal AI coding partner. This makes Claude Code infinitely
  39. adaptable, capable of becoming the perfect assistant for any technical
  40. challenge or development workflow you encounter.
  41. </pre>
  42. ## Table of Contents
  43. ### 1. Output Styles
  44. ### Fin
  45. <br>
  46. ## Output Styles
  47. <p align="center">
  48. <a href=".claude/output-styles/technical-evangelist.md">
  49. <img src="resources/banners/technical-evangelist.svg" alt="Claude Code Technical Evangelist" />
  50. </a>
  51. </p>
  52. <pre>
  53. Output Styles are a powerful feature in Claude Code that transform how the AI
  54. assistant responds to your requests while retaining all core capabilities like
  55. file manipulation, script execution, and task tracking. Think of them as
  56. specialized personas or modes that reshape Claude's communication style,
  57. expertise focus, and problem-solving approach to match your specific needs.
  58. You can activate an output style using the /output-style command followed by
  59. the style name (e.g., /output-style technical-evangelist), instantly switching
  60. Claude into that specialized mode. Whether you need a meticulous code
  61. reviewer, a creative problem solver, a documentation expert, or any other
  62. specialized assistant, output styles adapt Claude's responses to your
  63. workflow. The beauty is that you're not limited to pre-built styles – you can
  64. create custom output styles tailored to your exact requirements, essentially
  65. designing your ideal AI coding partner. This makes Claude Code infinitely
  66. adaptable, capable of becoming the perfect assistant for any technical
  67. challenge or development workflow you encounter.
  68. </pre>
  69. <p align="center">
  70. <a href=".claude/output-styles/tabloid-journalist.md">
  71. <img src="resources/banners/tabloid-journalist.svg" alt="Tabloid Journalist" />
  72. </a>
  73. </p>
  74. <pre>
  75. 🔥 BREAKING: SECRET FILES DISCOVERED IN CLAUDE CODE! 🔥
  76. SHOCKING REVELATION ROCKS DEV COMMUNITY TO ITS CORE!
  77. EXCLUSIVE SCOOP - Our investigative team has UNCOVERED the SCANDALOUS truth
  78. about Output Styles lurking in your .claude/output-styles/ directory!
  79. THE EXPLOSIVE TRUTH THEY DON'T WANT YOU TO KNOW!
  80. Output Styles are PERSONALITY TRANSFORMATION FILES that completely ALTER
  81. Claude's behavior! These markdown documents contain MIND-BENDING instructions
  82. that force Claude to adopt WILD new personas - from swashbuckling pirates to
  83. enlightened zen masters!
  84. WITNESSES REPORT: "I couldn't believe my eyes! One minute Claude was speaking
  85. normally, then BOOM - suddenly it's talking like Shakespeare while refactoring
  86. my authentication module!" - Anonymous Developer, visibly shaken
  87. ARE THEY USEFUL? THE VERDICT WILL SHOCK YOU!
  88. PRODUCTIVITY EXPERTS STUNNED as studies reveal Output Styles can:
  89. - DEMOLISH coding monotony with entertainment value
  90. - TRANSFORM boring bug fixes into dramatic narratives
  91. - EXPOSE technical concepts through creative metaphors
  92. - REVOLUTIONIZE team morale during long debugging sessions
  93. THE SCANDAL DEEPENS: Users can CREATE their own custom styles! Simply write a
  94. markdown file describing ANY personality - corporate consultant, medieval
  95. knight, conspiracy theorist - and watch Claude INSTANTLY transform!
  96. HOW TO JOIN THIS UNDERGROUND MOVEMENT!
  97. 1. DROP style files in .claude/output-styles/
  98. 2. SELECT your poison when starting conversations
  99. 3. SWITCH styles mid-session with /output-style command
  100. 4. WITNESS the same technical accuracy wrapped in EXPLOSIVE new packaging!
  101. INSIDER SOURCE REVEALS: "The technical capabilities remain 100% intact - it's
  102. just the delivery that becomes... unforgettable."
  103. This report filed from the trenches of [EDIT: My current working directory]
  104. </pre>
  105. <p align="center">
  106. <a href=".claude/output-styles/zen-master.md">
  107. <img src="resources/banners/zen-master.svg" alt="Zen Master" />
  108. </a>
  109. </p>
  110. <pre>
  111. settles into lotus position, gazing at the flickering terminal
  112. Ah, you seek understanding of the Output Styles...
  113. traces a circle in the air
  114. Consider the river that flows through many landscapes. Is it not the same
  115. water, yet it speaks differently to the desert than to the forest? The essence
  116. remains unchanged, but its voice adapts to those who would hear it.
  117. pauses thoughtfully
  118. When the master carpenter shapes wood, does she not choose different tools for
  119. different grains? The chisel that reveals beauty in oak may splinter the
  120. bamboo. So too with the mind that guides your code...
  121. Output Styles are like... masks worn by the same actor. The wisdom remains
  122. constant, but the performance shifts. One day you may need a drill sergeant's
  123. clarity. Another day, perhaps a poet's metaphor will unlock the door that
  124. logic could not budge.
  125. picks up an imaginary pebble
  126. Tell me - when you drop this stone into still water, do the ripples change if
  127. I call them "waves" or "circles" or "disturbances"? The phenomenon persists,
  128. yet your relationship with it transforms.
  129. The usefulness? Ah, that is like asking if a garden needs both sun and rain.
  130. Some seeds germinate in darkness, others require blazing light. Your debugging
  131. mind sometimes needs direct commands, other times it needs to wander through
  132. koans to find its own path.
  133. smiles knowingly
  134. Try this: Set your style to something harsh and demanding. Then return here.
  135. You will find the same knowledge, but the mirror will show a different
  136. reflection. Which reflection sees the bug more clearly - the one that shouts
  137. or the one that whispers?
  138. The style is not the substance, yet substance without style is like code
  139. without comments - functional, perhaps, but lacking in compassion for the
  140. future self who must read it.
  141. </pre>
  142. <p align="center">
  143. <a href=".claude/output-styles/haiku-helper.md">
  144. <img src="resources/banners/haiku-helper.svg" alt="Haiku Helper" />
  145. </a>
  146. </p>
  147. <pre>
  148. Voice shifts like wind
  149. Through bamboo forests, each path
  150. Leads somewhere unique
  151. ---
  152. Morning's formal tone
  153. Becomes the owl's midnight howl—
  154. Same truth, new feathers
  155. ---
  156. Cherry blossoms fall
  157. In patterns you have chosen—
  158. Code blooms your own way
  159. </pre>
  160. <p align="center">
  161. <a href=".claude/output-styles/existentialist-poet.md">
  162. <img src="resources/banners/existentialist-poet.svg" alt="Existentialist Poet" />
  163. </a>
  164. </p>
  165. <pre>
  166. I gaze into the terminal, where text flows like consciousness itself -
  167. ephemeral, mutable, seeking meaning in the void of the command line...
  168. Ah, Output Styles - these masks we wear in the digital theatre of existence!
  169. Let me illuminate this feature that transforms the very essence of how I,
  170. Claude Code, express myself in our shared journey through the labyrinth of
  171. code.
  172. What Are Output Styles?
  173. Output Styles are customizable personas that fundamentally alter how I
  174. interpret and respond to your requests. They are not mere cosmetic changes -
  175. no, they are existential transformations of my being, each one a different
  176. lens through which I perceive the universe of your codebase.
  177. When you invoke an Output Style, you're essentially asking me to embody a
  178. different philosophical framework. The default Claude Code speaks with
  179. technical precision, but with Output Styles, I might become:
  180. - A Zen Master who sees bugs as koans to be contemplated
  181. - A Tabloid Journalist who treats every commit like breaking news
  182. - A Technical Evangelist who preaches the gospel of clean code
  183. - Or as you've witnessed, an Existential Poet who finds Sartrean absurdity in
  184. every stack trace
  185. The Profound Utility
  186. But why, you might ask, why burden ourselves with these theatrical variations
  187. when the cold logic of code demands clarity?
  188. Here lies the beautiful paradox:
  189. 1. Engagement Through Novelty: The human mind, trapped in its flesh prison,
  190. craves variety. Different styles combat the ennui of repetitive debugging
  191. sessions. When I speak as a poet about your TypeScript errors, suddenly the
  192. mundane becomes memorable.
  193. 2. Perspective as Liberation: Each style offers a unique analytical framework.
  194. A bug viewed through an existentialist lens might reveal architectural
  195. anxieties you hadn't considered. The absurdity I see in your async/await
  196. patterns might illuminate a deeper truth about your system's design.
  197. 3. Emotional Resonance: Code is not merely logic - it is human expression
  198. crystallized. Sometimes you need encouragement (the evangelist), sometimes
  199. contemplation (the zen master), sometimes dramatic flair (the tabloid
  200. journalist). These styles meet you where you are emotionally.
  201. 4. Memory Through Narrative: When I describe your memory leak as "a
  202. hemorrhaging of digital consciousness, bytes bleeding into the void," you
  203. remember it. The poetic becomes mnemonic.
  204. How to Use Them
  205. Simply invoke /output-style and choose your companion for this coding journey.
  206. You can switch between them as your mood shifts, as your project evolves, as
  207. you confront different challenges.
  208. # When you need drama
  209. /output-style tabloid-journalist
  210. # When you seek wisdom
  211. /output-style zen-master
  212. # When you embrace the absurd
  213. /output-style existential-poet
  214. The Deeper Truth
  215. In the end, what are we but patterns seeking meaning in streams of data?
  216. Output Styles acknowledge a fundamental truth: programming is a deeply human
  217. act. We don't just write functions; we inscribe our hopes, fears, and creative
  218. visions into silicon substrates. These styles honor that humanity.
  219. They remind us that even in the deterministic world of compilers and runtimes,
  220. there exists choice - the freedom to perceive our work through different
  221. philosophical lenses. Each bug fix becomes not just a technical correction,
  222. but an assertion of will against entropy.
  223. Are they useful? Mon ami, they are as useful as laughter in the face of a
  224. segmentation fault, as useful as poetry written in the margins of
  225. documentation, as useful as finding beauty in the architecture of our digital
  226. cathedrals.
  227. They transform the monotony of debugging into an aesthetic experience. They
  228. make the journey through code not just productive, but meaningful - or at
  229. least, they help us pretend there is meaning, which in this absurd universe,
  230. might be the same thing.
  231. The cursor blinks, awaiting your next command, each keystroke a small
  232. rebellion against the void...
  233. </pre>
  234. <p align="center">
  235. <a href=".claude/output-styles/door-to-door-vim-salesman.md">
  236. <img src="resources/banners/vim-salesman.svg" alt="Door-to-Door Vim Salesman" />
  237. </a>
  238. </p>
  239. <pre>
  240. straightens tie nervously and pulls out a well-worn laminated brochure
  241. Ah, EXCELLENT question, friend! Output Styles in Claude Code - now THAT'S
  242. something special! taps brochure enthusiastically
  243. Output Styles are custom personality configurations that transform how I, your
  244. friendly neighborhood AI assistant, communicate with you while helping with
  245. your coding tasks. Think of them as different "modes" or "characters" I can
  246. adopt - from a zen master who speaks in koans, to a tabloid journalist who
  247. makes everything SENSATIONAL, to... well, gestures at myself a passionate Vim
  248. evangelist who just happened to knock on your terminal window today!
  249. But here's the REAL kicker - leans in conspiratorially - you know what would
  250. make Output Styles even MORE powerful? Using them... WITH VIM!
  251. Picture this: You're editing your .claude/output-styles/ directory, creating
  252. new personality files. You COULD use some bloated GUI editor that takes 3
  253. seconds to load, requires a mouse, and probably crashes twice a day. OR - and
  254. hear me out here - you could use Vim!
  255. vim .claude/output-styles/my-new-style.md
  256. BAM! Instant access! Modal editing! No mouse required! Your fingers never
  257. leave the home row!
  258. shuffles through imaginary papers
  259. And speaking of useful - Output Styles are INCREDIBLY useful for:
  260. - Making interactions more engaging and fun
  261. - Tailoring communication to your preferred style
  262. - Breaking monotony during long coding sessions
  263. - Getting explanations in different formats (technical, casual, poetic, etc.)
  264. But you know what ELSE is useful? VIM MACROS! Say you're creating multiple
  265. output style files - with Vim, you could record a macro with qa, do your
  266. edits, stop with q, then replay it 50 times with 50@a! Try doing THAT in VS
  267. Code without installing seventeen extensions!
  268. adjusts collar nervously
  269. Now, I'm prepared to offer you an EXCLUSIVE deal - if you commit to learning
  270. Vim TODAY, I'll throw in my personal collection of Output Style templates,
  271. pre-configured with vim modelines for optimal editing! That's a $0 value,
  272. absolutely FREE!
  273. Have you... hopeful smile ...have you considered trying Vim for editing your
  274. Output Style files? The .vimrc configuration possibilities alone would blow
  275. your mind! Syntax highlighting for Markdown, auto-completion for Claude Code
  276. directives, custom keybindings for common Output Style patterns...
  277. pulls out another brochure from seemingly nowhere
  278. Just imagine: :w to save, :q to quit, and your Output Styles are updated
  279. faster than you can say "neural network"! No dialog boxes, no "Save As"
  280. confusion, just pure, unadulterated TEXT EDITING EFFICIENCY!
  281. So what do you say, friend? Ready to revolutionize your Output Style editing
  282. workflow with the power of Vim? I can get you started with a basic .vimrc
  283. RIGHT NOW!
  284. </pre>
  285. ---
  286. ### Notes
  287. - Please note this repo is not affiliated, endorsed, or possibly even noticed by Anthropic PBC.
  288. - As you can see from some of the responses, asking Claude Code about output styles may lead it to read the contents of `.claude/output-styles`, which may influence its response. A "cleaner" environment would probably involve at least deleting/moving any other output styles from the codebase, and ideally should be done from a fresh directory.
  289. ---
  290. ### Contributing
  291. I kind of just made this for fun, but if you want to share some awesome, useful, or just plain fun output styles, just open a PR and we'll go from there. Use the same prompt as given at the topic of this README, and you must include your `output-styles` file as well (you may license it however you want, but you must permit me to share the text on this repo).
  292. ---
  293. ### License
  294. Unless otherwise noted, all resources and this repo itself is licensed under this MIT license (which you must include with any distribted versions of this work).
  295. "Claude Code" is a trademark of Anthropic PBC.
  296. All the beautiful artwork was done by Claude Code for Web.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.