docs

Automating API documentation generation extracts endpoints, schemas, and usage examples directly from your code and specs to output Markdown files under docs/api. This keeps your API docs in sync with your codebase without manual writing.

Generating component documentation from source definitions and usage patterns creates component docs automatically under docs/components. This eliminates manual updates and ensures your component documentation reflects the actual source code.

Keeping developer guides in sync with project changes uses a docs-generator orchestration to produce onboarding material from project context under docs/guides. This automated guide generation maintains accurate documentation as your project evolves.

Automated documentation generation requires no external dependencies to run, operating with an empty dependency list. You can generate and update API, component, and guide Markdown files directly within your codebase environment.

Updating existing Markdown documentation with latest codebase changes uses a doc-updater to modify files under docs/api, docs/components, and docs/guides. This ensures your existing documentation accurately reflects new endpoints and components.