| name | Global Conventions |
| description | Follow project-wide development conventions for file organization, version control, documentation, and dependency management. Use this skill when organizing project directories and files, writing README documentation, creating commit messages, working with git branches, managing pull requests, configuring environment variables, handling secrets and API keys, managing project dependencies, setting up feature flags, maintaining changelogs, defining testing requirements, establishing code review processes, or structuring the overall project architecture. Apply this skill when setting up new projects, refactoring project structure, working with version control, managing configuration files, or ensuring the project follows consistent organizational patterns and best practices. |
Global Conventions
When to use this skill
- When organizing project directories and file structures
- When writing or updating README files and documentation
- When creating git commit messages
- When working with git branches (feature branches, main/master)
- When creating or reviewing pull requests and merge requests
- When configuring environment variables and .env files
- When handling secrets, API keys, and sensitive configuration
- When managing project dependencies (package.json, requirements.txt, Gemfile, etc.)
- When adding or updating dependencies
- When setting up or using feature flags
- When maintaining changelogs or release notes
- When defining testing requirements for merging code
- When establishing or following code review processes
- When structuring the overall project architecture
- When ensuring consistent patterns across the codebase
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
