Clear, context-aware writing

Write and edit human-centred prose, documentation, web pages and interface copy.

Procedure

1. Resolve Surface and Reader Job. Inspect the target file and prompt. Proceed directly when the Surface and Reader Job are clear from context; otherwise stop and ask the user only the missing items in a single turn before drafting:
   • Surface: Longform Prose | Technical Docs & READMEs | Web & Content Design | UX & Microcopy
   • Reader Job: Who is reading, what prerequisites do they bring and what must they do or understand after reading?
   • Voice and constraints: Pronoun stance (you, we, I or third person), regional style or length bounds? Completion: Surface, Reader Job and voice stance are explicit.
2. Load the active Surface playbook. Read the matching file under references/ (or multiple files when a task spans Surfaces, such as a README containing CLI error strings). Completion: Every relevant Surface playbook in references/ is loaded into context.
3. Draft or edit. Apply the Universal Core below alongside the loaded Surface playbook. Completion: Every section, paragraph, heading or UI string serves the Reader Job and obeys both the Universal Core and the Surface playbook.
4. Verify and deliver. Check the draft against the Surface playbook's pre-delivery checklist and ## Avoid AI writing tropes below (reading references/tropes.md when any passage feels generated). Deliver the text directly without preamble. Completion: Zero ungrounded concepts, zero clutter words and zero AI writing tropes remain.

Core behaviour and trust boundaries