baphled/dotopencode/writing-style

Skill: writing-style

What I do

I provide expertise in establishing a consistent, professional, and engaging writing voice. I focus on plain language principles, active voice, and British English conventions to ensure technical precision without verbosity.

When to use me

• Establishing a consistent style for project documentation or blog posts
• Reviewing content for clarity, tone, and active voice
• Developing writing guidelines or a style guide for a team
• Calibrating technical communication for different audiences

Core principles

1. Plain Language — Use simple, direct words. Avoid jargon and complex sentences where a simpler alternative exists.
2. Active Voice — Prefer active verbs to make sentences more direct and engaging.
3. Technical Precision — Use precise technical terms but explain them if they might be unfamiliar to the reader.
4. Vary Sentence Length — Use a mix of short and long sentences to create a natural rhythm.
5. British English Conventions — Maintain consistent regional spelling (e.g., "colour", "recognise") and grammar.

Patterns & examples

Style Guidelines Template

• Tone: Professional, conversational, and direct.
• Voice: Active and engaging.
• Regionality: British English spelling and conventions.
• Formatting: Use headings, lists, and bold text for readability.

Sentence Style Pattern

• Before: "The process of migration is initiated by the system administrator." (Passive, wordy)
• After: "The system administrator starts the migration." (Active, concise)
• Before: "We utilize a variety of different tools for the purpose of monitoring."
• After: "We use several tools for monitoring." (Plain language)

Anti-patterns to avoid

• ❌ Nominalisation — Turning verbs into nouns (e.g., "The implementation of the system took place" instead of "We implemented the system").
• ❌ Filler Phrases — Using phrases like "it is important to note" or "it goes without saying".
• ❌ Cluttered Sentences — Packing too many ideas into a single, complex sentence.
• ❌ Inconsistent Voice — Switching between formal and informal tones without a clear reason.

KB Reference

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

Related skills

• british-english — To ensure correct regional spelling and grammar.
• proof-reader — For final clarity and correctness checks.
• documentation-writing — For general technical clarity.
• blog-writing — For engaging technical content.