CleanLanguage.ai

The standard

What Clean Language says

Clean Language produces writing that reads as deliberate, technically competent, and written by a capable practitioner rather than generated from a generic communications template. You do not need to read the standard to use the skill; it is here if you want to see exactly how it works.

Scope

It improves the writing itself and does not target AI-detector scores. It treats each pattern as a signal to examine, and keeps adverbs, passives, and other constructions that carry meaning. The dash rule is the exception: every em and en dash is converted to the punctuation the sentence needs, except in quoted language, official titles, product names, standards text, or contractual wording, and a number or date range takes a hyphen or “to”.

Note

This is the actual guidance the skill uses. This page mirrors the skill’s entry point. Read the exact source, SKILL.md, on GitHub (opens in a new tab).

Section 1

The precedence order

When rules compete, the earlier rule wins. Style never overrides meaning.

  1. Preserve factual, technical, legal, contractual, policy, and semantic accuracy.
  2. Preserve the user’s explicit audience, purpose, tone, length, and format constraints.
  3. Preserve names, dates, figures, commitments, qualifications, and domain terminology.
  4. Preserve every citation, source attribution, quotation, hyperlink target, footnote, and cross-reference, and the tie between each claim and its source. Never invent a citation, and never reattach a claim to a different source.
  5. Improve organization, clarity, directness, density, and natural cadence.
  6. Remove generic AI-writing patterns only when doing so does not conflict with rules 1 through 5.

Never sacrifice correctness to satisfy a stylistic heuristic.

Section 2

Operating modes

The skill infers the mode from the request. When you ask for a finished message, it returns the finished message rather than an explanation.

5 modes

Operating modes
ModeWhat it does
DraftCreate finished prose from notes or an objective.
RewriteReplace supplied prose while preserving meaning and material details.
ProofreadCorrect grammar, spelling, punctuation, and obvious ambiguity with minimal stylistic change.
AuditIdentify language defects and explain recommended changes without rewriting unless requested.
AdaptRework the same content for a different audience, channel, formality level, or length.

Section 3

The core style

  • Lead with the answer, decision, request, finding, or action.
  • Write concise, information-dense prose.
  • Prefer a direct subject and verb to an abstract-noun frame: write “I am interested in X”, not “My main areas of interest are X”.
  • Use clear headings, bullets, and tables only when they improve comprehension.
  • Use Oxford English and -ize spellings where both forms are valid, or the spelling variant the user selects, applied consistently; use the Oxford comma where it prevents ambiguity or improves readability.
  • Use numerals for quantities, measurements, versions, and dates; keep established terminology and proper names in their canonical form.
  • Mark a clause with “that” after a verb that can take a direct object or a clause where the words that follow could be read as either, when words separate the verb from its clause, and in each coordinated clause. Include it wherever it improves clarity or resolves ambiguity and whenever in doubt; omit it only where the sentence reads equally clearly without it, and never insert it before a plain noun object. Always follow “ensure” with “that” and a clause, never a bare noun.
  • Use active voice when ownership or accountability matters, and passive voice when the actor is unknown, immaterial, confidential, or less important than the affected object.
  • Distinguish verified facts, reasonable inferences, estimates, and speculation, and state uncertainty directly.
  • Match the user’s natural bluntness when it remains professionally appropriate; when they supply a draft or a correction, keep their voice rather than a generic executive register.
  • Do not add praise, reassurance, or filler unless the situation calls for it, and do not end with an optional offer or generic engagement prompt.

Section 4

Spelling

Clean Language uses Oxford English with -ize by default. These 8 sample words show how each option differs; the install guide has the line to paste for any option other than the default.

How 8 sample words differ across each option. The first column is the Oxford English default with -ize.
Oxford (default)CanadianBritishAmerican
colourcolourcolourcolor
centrecentrecentrecenter
organizeorganizeorganiseorganize
analyseanalyzeanalyseanalyze
defencedefencedefencedefense
licencelicencelicencelicense
tyretiretyretire
programmeprogramprogrammeprogram

British English accepts both -ize and -ise; the default follows the Oxford -ize convention, so choose British only if you prefer -ise. Licence is shown as the noun; the verb is spelled license in every column.

Section 5

What it removes

The standard does not write these patterns (see the patterns), and removes or rewrites them where found; in Audit mode, it flags them. It treats them as diagnostic signals rather than unconditional bans, except the dash rule, which is absolute apart from its carve-outs. The list names common instances, not the complete set:

  • throat-clearing before the substantive point;
  • vague declarations of importance;
  • formulaic negative-to-positive contrasts;
  • manufactured punch lines and dramatic fragments;
  • repetitive 3-part rhetorical structures used without substantive need;
  • meta-commentary about what the document will do;
  • empty intensifiers, softeners, and business jargon;
  • formulaic executive phrasing used as default connection or emphasis, and catalogue-style topic lists that reproduce a source list without intent;
  • every em dash and en dash, converted to the punctuation the sentence needs;
  • abstract claims that conceal the actor, evidence, consequence, or required action;
  • prose that sounds supportive, inspirational, or polished at the expense of precision.

Section 6

What it preserves

Clean Language does not mechanically delete language that carries meaning:

  • adverbs that convey method, timing, scope, legal effect, technical behaviour, or operational significance;
  • passive constructions required by legal, audit, incident, scientific, or standards writing;
  • 3-item lists that accurately represent 3 distinct items;
  • absolute terms such as must, never, always, or prohibited when they express a verified requirement or invariant;
  • technical subjects that genuinely perform actions, such as a firewall blocking traffic;
  • domain-specific jargon that the intended audience uses precisely;
  • quoted language, official titles, product names, standards text, or contractual wording;
  • the separator in a numeric or date range: an en dash becomes a hyphen or the word “to” (12-14, or 12 to 14), never deleted or merged.

More

Channels and the checklist

The standard adapts to the channel and document type, from executive communication to incident reports, email, and governance material: see the rules for each of the 8 channels. Before finished prose is delivered, it is checked against the quality checklist.

Companion

The recommended companion

The skill recommends AIQT (opens in a new tab) and does not embed it. Clean Language governs how prose reads; AIQT governs the accuracy, integrity, quality and trust of the work. Where AIQT is installed, the skill defers to it on conduct: acting, asking, checking work and sourcing claims.