What problem does it solve? Contributors often struggle to match a repository's established conventions for commit messages, code style, testing patterns, and common workflows, leading to inconsistent pull requests and repeated review cycles. ## Core Features & Use Cases - Commit Convention Guidance: Enforces conventional commit format (feat:, fix:, docs:, test:) with imperative mood and concise messages based on analysis of 500 real commits. - Code Style Standards: Documents naming conventions (camelCase files, PascalCase classes, SCREAMING_SNAKE_CASE constants), relative import style, and try-catch error handling patterns. - Workflow Templates: Provides step-by-step procedures for common tasks like adding new skills, agents, language rules, hooks, and syncing catalog counts. - Use Case: When adding a new feature to the repository, activate this skill to automatically follow the established pattern of implementing the feature, adding matching *.test.js tests, and writing a properly formatted conventional commit message. ## Quick Start Use the everything-claude-code conventions to implement this feature and write a properly formatted commit message.