init-contracts

To generate source-of-truth documentation directly from a codebase, you can automate the derivation of contracts and architecture docs from actual source code, avoiding guesswork and ensuring accuracy by performing code inventory and entry-point identification.

The best way to document architecture and patterns for an existing project is to derive them from the actual code structure, creating files like docs/ARCHITECTURE.md and a docs/patterns/ directory to capture architectural insights without manual guesswork.

Yes, you can auto-generate project contracts for any tech stack. The process works by analyzing the code structure and deriving documentation directly, ensuring accurate docs are produced regardless of the underlying technology.

To ensure generated codebase docs stay accurate, the documentation process requires targeted reads of the actual code inventory and entry-point identification, ensuring the derived contracts and architecture files reflect the current source of truth.

You should use automated code derivation instead of writing documentation manually when you need to bootstrap missing docs or refresh existing ones, ensuring your contracts and architecture files are accurate by deriving them directly from the source code.