project-conventions

To standardize coding conventions, document actionable guidelines for code structure, error handling, testing, and formatting in a Markdown file. This ensures consistent code quality and maintainability across the repository for developers, reviewers, and automation tooling.

Code conventions are documented patterns for code structure, error handling, and formatting. You need them to improve maintainability and streamline onboarding, PR reviews, and CI checks across your repository.

Create a style guide by writing actionable guidelines in a Markdown body, optionally referencing scripts, references, and assets directories. This provides documented patterns for reviewers and new developers during onboarding and PR reviews.

Yes, project conventions target automation tooling during CI checks by defining project-wide guidelines. Documenting these patterns ensures automated systems can validate code quality and maintainability consistently across the repo.

No dependencies are required to set up code patterns. The conventions use a lightweight starter template with a SKILL.md frontmatter and Markdown body, optionally referencing scripts, references, and assets directories when provided.