everything-claude-code-conventions

Conventional commits require prefixes like feat, fix, docs, or test to categorize changes. This standardizes commit history and aligns new contributions with the project's established formatting patterns.

JavaScript code style dictates camelCase for files and functions, PascalCase for classes, and SCREAMING_SNAKE_CASE for constants. Following these naming conventions ensures consistency across the codebase.

Workflow standards for adding new skills or commands involve step-by-step processes that match existing project patterns. This includes adhering to relative import syntax and mixed export patterns during development.

JavaScript contribution guidelines require a test coverage of 80% or higher. Adhering to these testing patterns ensures new code meets the project's quality standards before pull request review.

Relative import syntax in JavaScript specifies module paths relative to the current file. Enforcing this import rule standardizes dependency management and aligns with existing repository conventions.

You need contribution guidelines when submitting a pull request to avoid convention-related review feedback. Applying these standardized workflows speeds up merge times by ensuring code style and commits align.