Managing development conventions across teams is challenging and leads to inconsistent code quality. This skill guides Claude Code to follow your project-wide standards for structure, version control, documentation, and workflows.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「global-conventions」を使用しています。 Review my commit message: fixed bug
期待される結果:
Your commit message should follow the conventional format: type(scope): description. Consider: fix(auth): resolve token expiration issue in login flow
「global-conventions」を使用しています。 Where should I put my configuration files?
期待される結果:
Based on global conventions, configuration files should be organized as follows: environment-specific configs in /config directory, secrets in .env files (excluded from version control), and documentation in /docs. Always reference environment variables rather than hardcoding values.
セキュリティ監査
安全This skill is safe for publication. Static analysis detected 22 potential patterns but all were false positives. The skill contains only documentation and guidance references with no executable code. All network and filesystem detections were triggered by metadata fields and documentation text, not actual security risks.
品質スコア
作れるもの
Standardize Project Structure
Software engineers can ensure new features follow established directory layouts and file naming patterns
Enforce Git Workflow Compliance
DevOps teams can maintain consistent branch naming, commit message formats, and merge request standards
Maintain Documentation Quality
Technical writers can ensure README files, changelogs, and API docs follow organizational templates
これらのプロンプトを試す
Review my project structure and suggest improvements based on global conventions
Help me write a commit message for these changes following our team conventions
Set up environment configuration files following security and documentation best practices
Create a complete project structure with README, gitignore, and dependency files following our conventions for a new microservice
ベストプラクティス
- Reference the skill when starting new features to ensure proper project organization from the beginning
- Use the skill to review existing code before pull requests to catch convention violations early
- Combine with code review workflows to maintain consistent standards across the team
回避
- Do not use this skill to override security requirements or bypass necessary approval processes
- Avoid applying conventions blindly without understanding project-specific context and requirements
- Do not use outdated convention references without verifying they match current team standards