styleguide-check

To enforce consistent code style, load a shared rulebook and run an architecture checklist across structure, naming, comments, errors, logging, DB boundaries, patterns, and hygiene rules to validate changes against team standards.

Domain vocabulary drift occurs when synonyms replace agreed terms, causing inconsistency. You prevent it by loading a glossary document and treating any deviation from the shared vocabulary as a checklist failure during review.

You audit refactored routes and queries by loading both styleguide and glossary documents, then running the checklist across error handling, logging, database boundaries, and structural patterns to ensure operational safety matches standards.

Yes, you need a shared styleguide and glossary document. The quality guardrails require loading both files to audit structural consistency, naming conventions, and domain vocabulary before approving workflow logic changes.

If your code introduces synonyms for existing domain terms, it is treated as a synonym drift failure. The checklist actively cross-references the glossary to force vocabulary consistency and reject terminology changes.

Yes, you can use a code style checklist for both creating and reviewing workflow logic. Builders follow the rulebook before handoff, and reviewers use the same checklist to validate architecture, error handling, and operational safety.