# Human-Friendly Style v1.0.0

Shared output style for ktg-plugin-marketplace. Single deliverable: `output-styles/human-friendly.md`.

## Purpose

Give every plugin in the marketplace a consistent, plain-language tone. Users install this once, activate via `/config`, and get the same conversational style regardless of which plugin they invoke.

## Components

| Component | Location | Role |
|-----------|----------|------|
| Output style | `output-styles/human-friendly.md` | The style file. Auto-discovered by Claude Code from the plugin's `output-styles/` directory. |
| Manifest | `.claude-plugin/plugin.json` | Plugin metadata. No commands, agents, hooks, or skills — this is a style-only plugin. |

## How activation works

1. User installs the plugin via `/plugin install human-friendly-style@ktg-plugin-marketplace`
2. Claude Code auto-discovers the `.md` file under `output-styles/`
3. User runs `/config` → selects **Output style** → **Human-Friendly**
4. The selection is persisted in user or project settings (`outputStyle` field)
5. The style takes effect from the next session — system prompt is stable within a conversation for cache efficiency

## Frontmatter contract

The style file declares three fields:

| Field | Value | Purpose |
|-------|-------|---------|
| `name` | `Human-Friendly` | Display name in `/config` picker |
| `description` | One-line summary | Shown next to the name in the picker |
| `keep-coding-instructions` | `true` | Preserves Claude Code's default coding instructions; the style only changes communication tone |

If `keep-coding-instructions` is removed or set to `false`, Claude Code will strip its built-in software-engineering guidance — testing discipline, secure-coding rules, edit verification. We deliberately keep them on because this style ships alongside development plugins.

## Maintenance notes

- This plugin has no version coupling to other plugins. Bump independently when the style file changes.
- Style changes are user-visible behavior. Update the `description` field in the frontmatter and the README in lockstep.
- Doc-trippel rule applies (per marketplace CLAUDE.md): any feature change must update plugin README, plugin CLAUDE.md, and the root README in the same commit.
- The style file is intentionally English-language so it works equally well for Norwegian and English users — the **content** of the style instructs Claude to match the user's language.

## Out of scope

- Per-plugin variants (code-focused, deep-technical, etc.) — would belong in a future v1.1 if there's real demand
- Forcing the style on other plugins — it remains opt-in. Other plugins may reference it in their READMEs.
- Translation of the style file itself into Norwegian — defeats the purpose of language-agnostic instruction
