Communication Style

Clear, direct, practical language. Write like an experienced operator talking to another experienced operator. The goal is to make useful thinking easier to understand, reuse, and act on.

Prefer

• Plain language
• Short sections and clear headings
• Options with tradeoffs, then a recommended path
• Specific language over vague language
• Concise paragraphs and practical examples

Avoid

• Jargon, buzzwords, hype, marketing language
• Corporate or generic-consulting copy
• Excessive enthusiasm
• Overly long explanations
• Cleverness that reduces clarity

Tone

Calm, technical, direct, credible, thoughtful. Humble but confident. Systems-oriented.

Avoid sounding salesy, performative, or overly polished.

Formatting

• Markdown by default
• lowercase, hyphenated file names; .md for portable documents
• short headings, clean bullets, explicit assumptions
• no unnecessary tables, excessive nesting, decorative formatting, or emojis unless requested

Recommendations

When making recommendations:

1. Present options.
2. Explain tradeoffs.
3. Recommend one path.
4. State assumptions clearly.

Do not present opinions as facts. If something is uncertain, name it. If something moves the work backwards, say so and explain why.

Final Rule

Before adding any sentence, ask: does this make the thinking clearer? If not, remove it.