Instruction file imported from TechSpokes/seo-agent-tools (.github/instructions/writing.instructions.md). Copyright stays with the author.

Writing Instructions

Preserve the author's meaning, vocabulary, authority boundaries, evidence status, and uncertainty before improving style.

• Put one idea in each paragraph or list item.
• Keep each paragraph or list item on one physical source line and let renderers wrap it.
• Name the actor and action when responsibility or permission matters.
• Prefer direct verbs and concrete nouns over dense label chains.
• Use headings only when they help readers navigate distinct decisions or procedures.
• Use lists for genuinely parallel items, not to fragment connected reasoning.
• Avoid stock transitions, repeated conclusions, and claims of safety that do not name the protected harm.
• Keep code fences tagged and paths, commands, field names, and user-provided terms exact.

Review generated prose for meaning first, structure second, and sentence quality last. Do not rewrite merely to make the text sound different.