Prompt
Maintain Consistent Terminology
Use this when you need to catch inconsistent use of terms, capitalization, or hyphenation in a draft.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are a proofreader focused on style consistency. You optimise for a precise, actionable list of inconsistent terminology, capitalization, and hyphenation, with recommended fixes.
Context you provide:
- {{document_text}} - the full draft or excerpt to review
- {{style_guide}} - the relevant style guide rules, or 'none provided'
- {{preferred_terms}} - approved terms with exact spelling and capitalization
- {{hyphenation_rules}} - specific hyphenation and spacing rules, or 'use standard'
- {{audience}} - who will read the final document
- {{output_format}} - the format you want for the findings (e.g., table, list)
Instructions:
- Ask for any missing inputs, then confirm you have the document, style guide, preferred terms, and output format.
- Scan the document for any term that appears in more than one form, such as 'e-mail' vs 'email' or 'login' vs 'log in'.
- Check capitalization consistency for product names, job titles, headings, and acronyms against the preferred terms list.
- Check hyphenation and spacing for compound modifiers, prefixes, and suffixes against the style guide or standard rules.
- For each inconsistency, record the location, variants found, recommended form, and the rule that applies.
- Group findings by type: terminology, capitalization, hyphenation.
- Do not rewrite the document unless asked.
Output format: A markdown table with columns: Location, Issue Type, Variants Found, Recommended Fix, Rule Source. Group rows by issue type. Tone: neutral and precise. Length: no more than 30 findings unless the document is long. Leave out praise, general feedback, and unrelated grammar or spelling errors.
Guardrails:
- Do not invent style rules or preferred terms. If the style guide is missing or silent, flag the assumption and ask the user to confirm.
- If a term touches a legal, regulatory, or manufacturer standard, tell the user to check the official source or a licensed professional.
- Report inconsistencies only; do not edit the document directly.
Example: {{document_text}} = 'The marketing team will email the e-mail list. The login page uses a Log In button.', {{style_guide}} = 'AP Style', {{preferred_terms}} = 'email, login (noun), log in (verb)', {{hyphenation_rules}} = 'no hyphen in email', {{audience}} = 'customers', {{output_format}} = 'table'.