genesis-tools:living-docs

Automated codebase documentation uses a self-maintaining system to scan code, generate minimal doc chunks, and validate them against changes. This ensures documentation remains an accurate, token-efficient search index rather than a static textbook.

Documentation drift occurs when docs become inconsistent with code changes. Drift detection validates existing documentation against the current codebase, automatically flagging broken references and outdated API information for correction.

Bootstrapping documentation for reusable components involves scanning the codebase to identify utilities and complex flows, then creating minimal, token-efficient doc files using specific templates for features, components, and utilities.

Yes, documentation validation supports migration by operating in specific modes to update and migrate documentation formats. It refines existing docs for clarity, token efficiency, and better AI trigger activation during the transition.

Refining documentation for token efficiency is ideal when existing docs are structurally sound but verbose. The refinement mode optimizes doc chunks for clarity and better AI trigger activation, treating documentation as a search index rather than rewriting from scratch.