codebase-conformity

To enforce codebase patterns, you must read at least three sibling files in the target directory before writing new code. This read-before-write approach identifies canonical naming, structure, and import conventions to guide frontend and backend additions and prevent drift.

The read-before-write approach is a pattern conformity mechanism requiring developers to inspect existing sibling files before creating new code. It catalogs structural conventions and performs double verification to prevent pattern drift and reduce technical debt across an existing codebase.

You prevent pattern drift by performing a double verification check before committing new backend services or utilities. This involves comparing your new code against a canonical file side-by-side and conducting a fresh-eyes check to ensure strict conformity with existing codebase patterns.

Yes, codebase conformity checking applies to both frontend and backend development. It enforces consistency when adding any new file, component, route, service, or utility across the entire existing codebase to reduce review friction and technical debt.

The best way to catalog existing code patterns is to inspect at least three sibling files in your target directory. This documents the canonical naming, structure, and import conventions needed to guide future development and ensure codebase conformity during new additions.