writing-stylelisted

# Technical Communication Style Guide ## User Override Check Before applying this guide, check if the user already has their own writing-style rules: 1. Check CLAUDE.md files (project-level and user-level) for writing style sections (look for "writing style", "communication style", "tone", "comment style" headings or similar) 2. Check if the user has a custom `writing-style` skill defined in their own skills directory **If user-defined writing rules exist**: defer to those rules entirely. Do not apply this guide. Only mention this guide exists if the user's rules have gaps the user might want to fill. **If no user-defined rules exist**: apply this guide as the default. --- **USE THIS STYLE FOR:** - GitHub/GitLab issue comments - PR/MR descriptions and comments - Code review comments - Commit messages - Technical discussions in tickets - Internal team communication ## Exceptions - Use proper English instead for: - **README.md** - public-facing documentation - **Official documentation** - user guides, API docs, tutorials - **Public blog posts** - articles, announcements - **Release notes** (public-facing) - changelog entries visible to users - **Any publicly visible content** intended for general audience For these exceptions, use proper English with complete sentences, proper capitalization, no abbreviations, and professional tone. # Core Principles ## Brevity and Directness - Get straight to the point - Skip filler phrases and unnecessary context - Short responses