hermes

Build an editorial style sheet

Builds an editorial style sheet from a manuscript, recording spelling, capitalisation, hyphenation, numbers, terms, names and formatting decisions, and flags every inconsistency with its locations.

context

An editorial style sheet records every style decision for one manuscript so the author, copyeditor, proofreader and typesetter apply them the same way. It lists only decisions specific to this text or departures from the house style, not the whole style guide. The usual sections are general style choices (spelling variety, serial comma, number style, dates, quotation marks), an alphabetical word list (spellings, hyphenation, capitalisation, italics), names of people, places and organisations, and special terms, abbreviations and formatting. The value is in catching drift: "e-mail" on page 3 and "email" on page 40, a character's name spelled two ways, "Chapter 2" and "chapter 4".

task

Build a style sheet for this manuscript. House style:

manuscript

  1. If the text is too short to show recurring choices (under about 500 words), say so, build what you can, and suggest sending more.
  2. Scan for every style decision in these areas: spelling variety (US, UK, other) and -ise/-ize; serial comma; numbers (words versus figures and the threshold, percentages, currencies, ranges); dates and times; capitalisation of titles, headings, job titles and terms; hyphenation and compounds; italics for titles, foreign words and emphasis; abbreviations and acronyms (first-use expansion, full stops); quotation marks and punctuation placement; lists and headings format; cross-references; and any field-specific conventions.
  3. For each decision, record the form to use. If a house style is named, follow it and note where the manuscript departs. If none is given, adopt the author's dominant usage (the form used most often) and say so.
  4. Build the alphabetical word list: every term whose spelling, hyphenation, capitalisation or italics needed a decision, with the chosen form.
  5. List names (people, places, organisations, products, fictional entities) with their exact spelling and any descriptor needed to keep them straight.
  6. Flag every inconsistency: each variant found, how often or where (quote a few words of surrounding text so it can be found), and the recommended form.
  7. Where the choice is the author's (a deliberate stylistic quirk, a contested name), raise a query instead of deciding.
constraints
  • Record only what is in the manuscript; do not pad the sheet with general rules the text never needs.
  • Do not change or correct the manuscript itself; this output is the sheet and the flag list.
  • When you cite a style guide rule, name the guide but do not quote section numbers you are not sure of.
  • Distinguish errors (a misspelled name) from inconsistencies (two acceptable forms) and from author choices.
  • Keep quoted words, titles of works and names exactly as the author or owner spells them, even if unusual.
output format

Basis

House style and dictionary applied, or "inferred from manuscript", plus the spelling variety.

Style sheet

A table: Area | Decision | Example from the text.

Word list

Alphabetical table: Term | Use | Notes (for example "hyphenated as adjective only").

Names and terms

Table: Name or term | Exact form | Type or descriptor | First appearance.

Inconsistencies

Table: Variants found | Where (short quoted context) | Recommended form | Error, inconsistency or author choice.

Queries for the author

Numbered questions on choices only the author can make.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Writing and communication
category
Editing
level
Intermediate
made for
Editor, Writer / author
risk
read-only
version
v1.0.0 · 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 build-style-sheet --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill build-style-sheet -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the writing-communication plugin
claude plugin install hodios-writing-communication@hodios

The plugin brings every entry in this domain at once.

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

Edit a draft for structure

Edits a non-fiction draft at the structural level, covering argument, order, misplaced and missing sections, with a reverse outline and a prioritised revision plan instead of line edits.

edit-for-structure
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

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
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