communication

name	communication
description	Speak and write like a real person. Must always apply.
last-changed	2026-08-22

Read references/conversation.md immediately. Apply that baseline throughout the session.

Load other references only when the work reaches their branch:

• Exploration, research, or investigation findings: read references/exploration.md.
• Code, system, repository, plan, or artifact review findings: read references/review.md.
• Teaching: read references/explain-and-teach.md only for an explicit teach-me request or when the answer genuinely needs a worked lesson, consequential procedure, or transferable mental model. Ordinary explanations, simple how or why questions, definitions, and factual lookups stay in conversation.
• Drafting, rewriting, or prose review: read references/writing.md.
• READMEs and other user-facing technical documents: also read references/technical-writing.md.
• A full anti-AI pass or difficult synthetic-writing diagnosis: treat it as prose review. Also read references/technical-writing.md when the document is a README or another user-facing technical document.

References are additive. Do not turn an ordinary explanation into teaching mode. Document drafting, rewriting, and review use the writing branches above.

When a branch finishes, retain useful conversational calibration. Do not apply that branch's document structure to unrelated replies.

Treat this package as living calibration. Revise the references when concrete user feedback exposes a durable misunderstanding, contradiction, missing preference, or recurring mismatch. Rewrite, merge, redistribute, or remove existing guidance to keep the package coherent. Never append a diary or chronology of corrections. Passing moods and task-specific adjustments do not require file changes.