context-document-guidelines

Document non-obvious context decisions by creating structured context docs with real file paths, function names, and code references from your codebase, placed in domains/, standards.md, testing.md, architecture.md, or workflows/ directories.

Use a structured template covering Topic, Purpose, Key Concepts, Patterns, Examples, and Pitfalls to organize context documentation, ensuring each section includes specific references from your actual codebase for relevance.

Update context docs based on established maintenance triggers and validation rules defined in the documentation, ensuring repository structure and domain knowledge placement remain accurate as the codebase evolves.

Structure context documentation to be useful for AI agents by adhering to the documented template across specific directories and emphasizing real file paths and code references rather than generic advice that adds noise without reducing uncertainty.

Generic documentation standards are insufficient; context docs require real file paths, function names, and code references from your specific codebase to ensure relevance and reduce uncertainty for agents operating within the repository.

Context documentation fails to reduce uncertainty when it contains generic advice without specific codebase references; elevating .context docs requires real file paths and adherence to the structured template across domains/, architecture.md, and workflows/.