follow-existing-patterns

To enforce code consistency, manually validate new code against established conventions and patterns. This ensures new features match existing coding styles, error handling, and status message formats, preventing structural inconsistencies that require rework.

Maintaining documentation standards requires ensuring new docs follow a uniform structure and formatting. By validating documentation against established codebase conventions, you guarantee menu items are formatted uniformly with consistent numbering and descriptions.

Yes, convention enforcement requires manual review and validation of new code and documentation. You must actively compare new implementations against established patterns to ensure adherence to the codebase's existing style, structure, and error handling.

Before implementing a new feature, review the codebase to identify established coding styles, error handling, and status message formats. Use this analysis to validate new code matches existing conventions and reduces the need for rework.

New code requires rework when it fails style guidelines because it introduces inconsistencies into the codebase. Enforcing adherence to existing conventions and patterns during development prevents structural mismatches and improves long-term maintainability.

Yes, convention enforcement applies to configuration consistency. You can validate configuration files against established codebase conventions to ensure uniform structure, style, and formatting across the software development workflow.