baphled/dotopencode/british-english

Skill: british-english

What I do

I provide expertise in enforcing British English spelling, grammar, and conventions in all written content. I ensure consistency across documentation, commit messages, and user interfaces by following UK standards.

When to use me

• When writing or reviewing documentation and README files
• When creating user-facing labels, messages, or descriptions
• When drafting technical articles or blog posts for the project

Core principles

1. Spelling consistency: Use -ise over -ize and -our over -or where applicable.
2. Date formatting: Use the DD Month YYYY format (e.g., 22 February 2026) to avoid ambiguity.
3. Punctuation: Place punctuation outside quotation marks unless it is part of the original quote.
4. Collective nouns: Treat collective nouns (e.g., "the team", "the company") as plural when they refer to the individuals within the group.

Patterns & examples

Common spelling differences:

Date and time:

• ✅ 22 February 2026
• ❌ February 22nd, 2026
• ✅ 21:00 (24-hour clock preferred in technical contexts)

Grammar and punctuation:

• ✅ The government are considering the proposal. (Plural verb for collective noun)
• ✅ Use the "save" button. (Punctuation outside quotes)
• ✅ He said, "The build failed." (Punctuation inside when part of the quote)

Anti-patterns to avoid

• ❌ Mixing variants: Do not use British spelling in one paragraph and American in the next.
• ❌ Oxford comma misuse: While optional, be consistent. In British English, it is generally used only to avoid ambiguity.
• ❌ -ize suffixes: While some British dictionaries accept -ize, -ise is the standard for most UK publications and projects.

KB Reference

~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/Communication-Writing/British English.md

Related skills

• writing-style: For overall tone and voice consistency
• documentation-writing: For structuring clear and helpful guides
• proof-reader: For final checks on grammar and spelling