---

name: Global Conventions description: Follow project-wide development conventions including consistent project structure, clear documentation, version control best practices, environment configuration, and dependency management. Use this skill when organizing project structure or directories, writing or updating README files, creating documentation, writing commit messages, managing environment variables or configuration files (.env, config files), managing dependencies (package.json, requirements.txt, Cargo.toml, go.mod), implementing feature flags, maintaining changelogs, setting up code review processes, or defining testing requirements. Use across all project organization work regardless of language or framework, including when working with version control, project configuration, or development workflows.

When to use this skill

• When organizing project structure or directory layouts
• When writing or updating README files, documentation, or contribution guidelines
• When writing commit messages or creating pull/merge requests
• When managing environment variables or configuration files (.env, config.yml, settings files)
• When managing project dependencies (package.json, requirements.txt, Cargo.toml, go.mod, Gemfile)
• When implementing feature flags or configuration toggles
• When maintaining changelogs or release notes
• When setting up or following code review processes
• When defining testing requirements or coverage expectations
• When ensuring secrets or API keys are not committed to version control
• When creating or updating architecture documentation
• When establishing project-wide conventions or standards
• When working with version control systems (Git, SVN, Mercurial)

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