project-conventions

To document coding standards for a codebase, you define standard patterns, naming conventions, folder structures, and review processes in a central reference, creating a single source of truth for consistent practices across teams.

Project conventions are documented patterns and standards for building and maintaining a codebase. You need them when onboarding new contributors, enforcing coding standards, or auditing architecture to ensure consistency across teams.

You standardize folder structure and naming conventions by documenting the team's actual patterns as a single source of truth, replacing placeholder patterns to enforce consistent codebase practices and architecture audits.

Yes, you can use this to onboard new contributors by providing a descriptive central reference of the project's actual conventions, serving as the authoritative source for standard codebase patterns and review processes.

The best way to enforce coding standards during architecture audits is to maintain a documented set of project conventions, providing a single source of truth to verify consistent patterns and structural compliance across the codebase.

Documenting project conventions requires no specific dependencies, but it satisfies requirements for YAML frontmatter with name and description, a descriptive Markdown body, and discovery-ready metadata to standardize the codebase.