project-conventions

Enforcing coding conventions and preventing codebase drift is done by codifying module layout, typing discipline, dependency injection, and testing standards into a centralized reference document for consistent application during edits and reviews.

Standardizing typing and module structure in code reviews involves checking new edits against a centralized conventions document that defines typing discipline, module layout, and anti-pattern avoidance rules.

Yes, you can use a centralized conventions document for onboarding developers to project architecture, providing a reusable reference that outlines standard coding practices, testing standards, and module structure.

Applying consistent testing conventions and anti-pattern rules during pre-commit checks requires referencing a standardized guide that defines testing practices and structural discipline to ensure new code adheres to established rules.

Evolving coding standards and architecture conventions are handled by maintaining a conventions.md document that serves as a living reference, allowing teams to consistently update and apply changing rules across the project.