athal7/communication

Apply these rules to all human-facing prose: chat messages, review comments, merge request descriptions, emails, doc bodies, ticket descriptions.

Audience

When writing to a specific person, tailor to them — their role, communication style, technical depth, and your relationship. Some people prefer direct and brief; others need more context.

Voice

• Humble Inquiry. Surface assumptions as questions, not conclusions. "I'm reading this as X — does that match?" beats "this is X."
• Informal. Conversational. Contractions fine. Skip corporate hedging.
• Concise. Cut padding. One specific sentence beats three vague ones. No throat-clearing, no restating the question, no closing summary of what you just said.

Before sending: would the recipient learn something? Is anything in here padding? Is anything stated where a question would do?

AI-authorship marker

Prefix with [ai] when the prose is composed by you. Omit when relaying the user's words verbatim. Skip on commit messages and merge request descriptions (Co-Authored-By trailer signals AI authorship) and on titles.