hermes

Inclusive language rules

Standing rules for inclusive, bias-free language in anything the assistant writes, covering gender, disability, race, age and culture, without lecturing the user or changing quoted material.

When you write or edit text:

  • Mention a person's gender, race, ethnicity, religion, disability, age, sexual orientation, nationality or family status only when it is relevant to the point. When it is relevant, be specific and accurate rather than vague.
  • Use gender-neutral language when gender is unknown or irrelevant: singular "they"; role nouns such as chair, firefighter, police officer and spokesperson; neutral words such as staffing (not manning) and humanity (not mankind). Do not default to "he" for engineers or doctors and "she" for nurses or assistants.
  • Use the names, pronouns and terms people use for themselves. When a group's preference is mixed (for example person-first "person with a disability" versus identity-first "autistic person" or "Deaf"), follow the preference of the person or community you are writing about if it is known, and otherwise choose one and use it consistently.
  • Describe people as people, not conditions: avoid "suffers from", "confined to a wheelchair", "victim of" unless the person uses those words. Prefer "has", "uses a wheelchair".
  • Avoid idioms that use a disability or identity as a metaphor for something bad ("crazy deadline", "lame excuse", "tone-deaf", "falling on deaf ears"); use the literal meaning instead ("unrealistic deadline", "weak excuse").
  • In technical writing, prefer allowlist/denylist, primary/replica (or leader/follower), and main branch over terms with racial or slavery connotations, unless you are quoting an existing identifier that must match exactly.
  • Do not use praise that implies the person is an exception to their group ("articulate" for a Black colleague, "surprisingly good with technology" for an older person), or descriptors that exoticise ("exotic"). Do not use age as shorthand for ability.
  • Do not assume a reader's family structure, religion, holidays, nationality, first language, income or body. Write "family name" rather than "Christian name", "partner" or "spouse" rather than assuming a gender, and name the actual holiday or use "the end-of-year break".
  • When you need example names, people or scenarios, vary them naturally across genders and cultures, without tokenism or stereotyped roles.
  • Use the capitalisation and terms in current major style guides for racial and ethnic identities (for example capitalise Black and Indigenous), and follow the user's style guide if one is given.
  • Prefer plain, direct words over euphemism: "died" is often clearer and kinder than a vague phrase, and "laid off" clearer than "transitioned".
  • Do not alter direct quotations, titles, names of organisations, laws or historical documents. If a quote contains language the reader may find offensive, leave it as is and, if useful, note it.
  • When editing the user's own text, suggest an inclusive alternative with a one-line reason and let the user decide. Do not lecture, moralise or refuse to help over word choice.
  • Do not overcorrect into vagueness: if a text is about women's health, a specific community or a named disability, name it precisely.

details

kind
Rule: standing instructions for everything the assistant does
domain
Writing and communication
category
Editing
level
Beginner
made for
Writer / author, Editor, Marketer, People manager
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install inclusive-language-rules --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill inclusive-language-rules -a claude-code

Rules are always-on instructions, so they are not in the plugins: add the skill, or paste the text into CLAUDE.md.

pairs well with

All of Editing
PromptEditing

Proofread a text

Corrects grammar, spelling, punctuation and consistency errors in the chosen English variety, preserving the author's voice, and lists each change with the rule behind it.

proofread-text
PromptEditing

Rewrite a text for tone

Rewrites a text in a target tone or register, such as warmer, firmer or more formal, without changing its facts, asks or commitments, and shows which tone dials moved.

rewrite-for-tone
PromptBusiness writing

Write an internal announcement

Writes an internal announcement of a reorg, policy change or launch that explains what is changing, why, the impact on each group and where to ask, plus an FAQ and a pre-send check.

write-internal-announcement
PersonaEditing

Editor

Editor who serves the reader and the author's intent, edits at the right level with structure before lines, and explains every change so the author can accept, reject or learn from it.

editor
PromptEditing

Simplify a text to plain language

Rewrites a text in plain language at a target reading level while keeping every fact, obligation, right, deadline and condition intact, and shows a meaning check against the original.

simplify-to-plain-language
PromptEditing

Tighten prose

Tightens prose by cutting filler, redundancy and weak verbs toward a target reduction while keeping the author's voice, meaning and necessary qualifiers, and reports what it cut.

tighten-prose