update-spec

To document code specification conventions after a bug fix, you update code-specification documents with executable contracts derived from development insights, capturing design decisions and forbidden patterns to maintain institutional memory.

An executable contract in code specification documents is a structured record of project conventions, design decisions, and new patterns that enforces a code-spec first philosophy for implementation details and cross-layer contracts.

You capture development insights and gotchas into structured spec files by systematically updating backend, frontend, and guide documentation with new patterns and common mistakes discovered during debugging and project discussions.

Yes, the code-spec first philosophy supports both frontend and backend knowledge management by organizing and refining executable contracts within dedicated spec files for each specific layer and project guides.

The best way to maintain institutional memory for project conventions is to systematically capture valuable learnings from development and discussions, updating structured spec files with design decisions and cross-layer contracts.

You should update spec files with new development patterns immediately after fixing bugs or making design decisions, ensuring that new conventions, forbidden patterns, and gotchas are systematically captured for future reference.