Follow consistent project structure, version control practices, environment configuration, code review processes, and development conventions across the entire application. Use this skill when organizing project files and directories, when writing commit messages or creating pull requests, when managing environment variables and configuration, when participating in code reviews, when defining testing requirements, when using feature flags, when maintaining changelogs, when documenting setup instructions, or when establishing consistent development practices across the team.
Content & Writing
85 Stars
2 Forks
Updated Jan 19, 2026, 04:39 AM
Why Use This
This skill provides specialized capabilities for aiskillstore's codebase.
Use Cases
Developing new features in the aiskillstore repository
Refactoring existing code to follow aiskillstore standards
Understanding and working with aiskillstore's codebase structure
---
name: global-conventions
description: Follow consistent project structure, version control practices, environment configuration, code review processes, and development conventions across the entire application. Use this skill when organizing project files and directories, when writing commit messages or creating pull requests, when managing environment variables and configuration, when participating in code reviews, when defining testing requirements, when using feature flags, when maintaining changelogs, when documenting setup instructions, or when establishing consistent development practices across the team.
---
# 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.
## When to use this skill
- When organizing or restructuring project files and directories
- When writing commit messages, creating branches, or making pull requests
- When managing environment variables and configuration files
- When documenting features in README files or architecture documentation
- When participating in code reviews as reviewer or author
- When defining or following testing requirements before merging
- When implementing feature flags for incomplete or experimental features
- When maintaining changelog or release notes
- When managing project dependencies and documenting why they're used
- When setting up or updating contribution guidelines
- When ensuring consistent practices across the development team
- When making decisions about long-lived branches vs. feature flags
## Instructions
For details, refer to the information provided in this file:
[global conventions](../../../agent-os/standards/global/conventions.md)
