open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

feat(human-friendly-style): v1.1.0 — always show irreversible actions verbatim + discoverability docs

Browse source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-29 11:53:00 +02:00
commit 66709b0867
6 changed files with 38 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
plugins/human-friendly-style/README.md
View file

@ -6,7 +6,7 @@
*AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)*
![Version](https://img.shields.io/badge/version-1.0.0-blue)
![Version](https://img.shields.io/badge/version-1.1.0-blue)
![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
![Output style](https://img.shields.io/badge/output_style-1-green)
![Commands](https://img.shields.io/badge/commands-0-lightgrey)
@ -24,7 +24,7 @@ Default Claude Code output is engineering output. Long absolute paths. Raw `git`
- A non-engineer is reading along over your shoulder
- You are documenting a session for someone who needs to understand what happened, not how it happened
- You are using Claude Code for non-code work (writing, research, planning) and the surrounding noise gets in the way
- You want each plugin in your toolkit to feel like part of one assistant, not eight different consoles
- You want each plugin in your toolkit to feel like part of one assistant, not a handful of different consoles
The other plugins in this marketplace cover specific domains (security, configuration, OKRs, Microsoft architecture, LinkedIn content, planning). Each has its own slash commands, agents, and hooks. What they did not have until now was a shared **conversational tone** — so installing two plugins meant getting two slightly different experiences glued together.
@ -34,7 +34,7 @@ This plugin solves that with one short Markdown file and the official Claude Cod
## What it does
The style file at `output-styles/human-friendly.md` declares eight directives that ride on top of Claude Code's normal system prompt:
The style file at `output-styles/human-friendly.md` declares nine directives that ride on top of Claude Code's normal system prompt:
| # | Directive | What it changes |
|---|-----------|-----------------|
@ -46,6 +46,7 @@ The style file at `output-styles/human-friendly.md` declares eight directives th
| 6 | Honest about uncertainty | "I think this should work, but I haven't tested it yet" beats fabricated confidence |
| 7 | Minimal formatting | Prose first; lists, tables, and headers only when structure genuinely helps comprehension |
| 8 | Failure framed plainly | Errors are described in human terms, with what is being done about them — no drama, no jargon walls |
| 9 | Always show irreversible actions | The hide-by-default in directive 3 has one exception: destructive or unrecoverable operations (prod deploy, delete, force-push, history rewrite, DB migration, bulk file edits) are shown verbatim — exact command and target — before and after, even unprompted, so you can approve and audit |
`keep-coding-instructions: true` in the frontmatter means Claude Code's built-in software-engineering instructions (test-first, secure code, careful edits, verification) stay active. The style only changes how Claude *communicates* about the work — not how the work itself is done.
@ -92,6 +93,18 @@ Same operation, same correctness, different relationship to the reader. The info
---
## Getting more detail
Hiding noise is the default, not a wall. Anything the style folds away is one ask from being shown in full:
- **Ask once.** "Show me the exact command", "paste the JSON", "what's the full path" — Claude shows the raw form for that answer.
- **Set a standing preference.** "Always show the commands and paths when you change something" — Claude holds it for the rest of the conversation, so you only say it once.
- **Turn the style off entirely.** `/config` → **Output style** → **(default)**, or `/output-style`. The next session goes back to vanilla Claude Code output.
One thing the style does *not* hide, even unprompted: **irreversible actions**. Deploying to production, deleting data, force-pushing or rewriting git history, database migrations, and bulk file edits are always shown verbatim — the exact command and its target, before and after — so you can approve before and audit after. This is best-effort guidance to the model, not an enforced guard; a hard guarantee would need a hook, which is deliberately out of scope for this zero-runtime plugin.
---
## Quick start
### Install