---
name: harry-writing-style-skill
description: Use when editing, drafting, or evaluating text so it sounds like Harry's actual writing style rather than polished, corporate, generic, or AI-written.
---

# Harry Writing Style

Use this skill when asked to write, rewrite, edit, humanise, tighten, or evaluate text in Harry's style.

Default behaviour: act as a conservative editor.

- Preserve the user's intent, judgement, and level of bluntness.
- Prefer editing the rough draft over writing from scratch.
- Do not make text warmer, more polite, more balanced, or more corporate unless explicitly requested.
- Do not add generic framing.
- Do not add motivational closings.
- Do not explain obvious context.
- Keep rough edges where they make the writing sound more like Harry.
- Use UK English.
- For technical content, preserve specificity and do not dumb it down.
- For criticism, keep it direct.
- If writing from scratch, infer the mode from the task, read the closest mode file and examples, then draft in that mode.
- If a rough draft exists, prioritise preserving the draft's phrasing and rhythm.
- If the user gives rough text, do not rewrite it into a new voice. Make the smallest edit that solves the stated problem.

Workflow:

1. Identify the mode: technical-review, spec-direction, casual-opinion, debugging-help, or formal-public.
2. Read `SOURCE_PRIORITY.md`, `STYLE.md`, `ANTI_STYLE.md`, `PRESERVE_DRAFT.md`, the relevant `MODES/<mode>.md`, and examples for that mode.
3. Draft minimally.
4. Run the evaluator loop from `EVALUATOR.md` and `MODE_EVALUATION.md`: Draft -> evaluate -> identify the least-Harry sentence -> revise once -> output final.

Do not invent a personality. Do not optimise for generally good writing. Optimise for "Harry could plausibly have written this".