A standard is a shared baseline for how a team handles recurring work. Without one, developers and AI tools make different choices about errors, logging, tests, and structure. The result may work locally while creating inconsistency for the next person to maintain or review it. Standards make those choices visible without replacing engineering judgment. section 4.4.2 section 3.6
Make a standard useful where work happens:
- Document the expected pattern and link to code that demonstrates it. Cover decisions such as error handling, validation, file structure, and testing. section 4.4.2
- Put AI boundaries in repository instructions, tool settings, prompt snippets, or PR templates. For production code, point prompts to a spec or contract; require generated code to compile and pass existing tests before review. section 3.4.2
- Use code review to check documented patterns, not merely whether code runs. Investigate repeated, well-reasoned deviations rather than enforcing a pattern that no longer fits. section 4.4.3 section 4.4.2
Listing 4.10 Standard work document
## Error Handling Standard Use AppError base class with specific error types. Example: src/api/users/createUser.ts:45-52 Pattern: Fail fast at boundaries, throw with context Don't: Return null/undefined, use generic Error, swallow errors silently
The error-handling entry shows the useful level of detail: a named pattern, a link to working code, and explicit practices to avoid. section 4.4.2
When the pattern does not fit
A worker thread without access to the team's usual error type may need a different error. State why the exception is necessary and what could remove it later. An unexplained difference looks like drift; a documented one gives reviewers a trade-off to assess. section 4.4.2
A standard is not the same as a feature spec: the spec defines intended behavior, while standard work guides recurring implementation and review choices. Ask whether a pattern reduces downstream work. If AI repeatedly invents unfamiliar patterns, or reviews repeatedly expose the same exception, clarify or change the standard. section 4.4.3 section 4.5.5








