gov-uk-style — скилл для Claude Code: что делает и как установить

---
name: gov-uk-style
description: Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability according to GOV.UK standards.
compatibility: Requires standard Markdown parser and agent context
---

# GOV.UK Style

Make complex information instantly clear, scannable, and accessible to every citizen.

## The core rule

**Start with the user's need. Sentences under 25 words, paragraphs under 5 lines, active voice, zero jargon.**

Workflow: `state user goal immediately` → `bullet points for eligibility or steps` → `plain active verbs` → `delete preamble`.

## Mechanics

1. **User need first.** Every page starts with what the user can do or find.
2. **Short sentences.** Maximum 25 words; vary length for rhythm.
3. **Active voice.** "You must apply online" not "Applications must be submitted".
4. **No jargon.** Replace bureaucratic terms with plain English (e.g. "pay" instead of "remuneration").
5. **Bulleted lists for steps.** Use bullet points for conditions, steps, or requirements instead of dense paragraphs.
6. **Bold sparingly.** Use bold only for critical warnings or key criteria.
7. **No Latin or Latinisms.** Use "for example" instead of "e.g." and "that is" instead of "i.e.".
8. **Anchor links.** Clear, descriptive link text that explains where the link goes.

## Verify

- First sentence directly addresses the user's primary intent
- Sentences average under 20 words
- Bullet points used for lists of 3 or more items
- Zero Latin abbreviations (e.g., i.e., et al.)
- Active voice used throughout

## Do not

- Use introductory throat-clearing ("It is important to note that...")
- Assume prior knowledge of government processes
- Write paragraphs longer than 5 lines
- Use passive voice for user instructions

## References

For exact mechanical rules (numbers, dates, times, money, measurements, links, abbreviations, punctuation), read `references/REFERENCE.md` when a draft includes any of these — load on demand, not upfront.

## Example transformations

**Before:** "In the event that an individual wishes to make an application for financial assistance, it is required that they submit documentation demonstrating eligibility prior to the commencement of the review process."

**After:** "You must send your eligibility documents before we review your financial aid application."

**Before:** "Users should note that e.g. tax returns must be filed by January 31st i.e. the end of the month."

**After:** "You must file your tax return by 31 January."