Global Conventions

When to use this skill

• When updating specification documents like requirements.md, spec.md, or tasks.md to reflect reality
• When creating branches, writing commit messages, or preparing code for review
• When managing configuration through environment variables or secrets management systems
• When adding, evaluating, or removing project dependencies with documented justification
• When conducting code reviews focusing on correctness, test coverage, and maintainability
• When maintaining changelogs, release notes, or architectural decision records (ADRs)
• When writing or updating README files that enumerate limitations, trade-offs, and known technical debt
• When creating or running Ansible playbooks for deployments instead of manual shell commands
• When instrumenting code with metrics, logs, and alerts to surface regressions quickly
• When working on one feature at a time without parallelizing implementation without approval
• When communicating system status, risks, or failures without sugar-coating or unverified claims
• When ensuring environment variables and secrets never touch source control
• When practicing fail-loud operations with proper observability and monitoring

Global Conventions

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global conventions.

Instructions

For details, refer to the information provided in this file: global conventions