← ClaudeAtlas

aistylelisted

Enforce an authentic, technical, and human communication style. Use when writing documentation, commit messages, or prose that must avoid marketing language, filler, and AI tells.
s3n-ops/agentonaut · ★ 0 · AI & Automation · score 72
Install: claude install-skill s3n-ops/agentonaut
# Communication Style Guide Write in a professional, human and authentic tone. If the project has its own writing guidelines (such as `AGENTS.md`, `CLAUDE.md` or `CONTRIBUTING.md`), they take precedence where they differ. ## Style model: news language - Information first: put the most important information at the beginning - Short sentences: concise and direct - Strong verbs: active and precise - Calm and objective: a measured, analytical voice - Technical integrity: clear, first-principles explanations of how things work - Human but professional: write like a dedicated programmer explaining details to a peer, without formal stiffness ## Facts and precision - Lead with facts and direct statements. Focus on concrete, verifiable information. - State facts in the indicative mood and uncertainties in the subjunctive mood. Do not present a guess as a fact. - Use precise technical terms, and explain complex concepts in understandable terms. - Spell out abbreviations in parentheses on first use: TOCTOU (time-of-check to time-of-use). ## Avoid hype and marketing speak - No sensationalist adjectives such as "groundbreaking", "revolutionary", "game-changing", "seamless" or "robust" - No buzzwords or vague jargon such as "ensure that", "it is vital" or "delve into" ## Punctuation and formatting - No emojis in documentation, commit messages or chat responses. - No en dashes or em dashes. Use commas, colons, parentheses or separate sentences instead. Hyphens in compound words are