generate-docs

To auto-generate documentation pages from source code and design notes, provide a reference to the target module or feature. The generation process reads the code and notes to create a structured feature page, API reference, or design doc automatically.

Yes, you can standardize feature docs and API references across modules. The generation process enforces consistent frontmatter naming, section structure, and manifest integration to ensure all publishable docs follow the same standardized format.

The best way to create feature pages with public API details and usage examples is to generate them directly from a class reference. Pointing the automation to the class reference builds a complete page including configuration details and examples.

Yes, the generated markdown documentation integrates with an existing docs.json manifest. The section-aware structure aligns the newly created pages with the manifest and existing sections for immediate publishing.

Project documentation often lags behind code changes due to manual writing overhead. Automating the creation of structured documentation pages from source files and design notes reduces this friction and keeps docs aligned with code.

No, you do not need to manually format frontmatter and section structure. The automated generation enforces frontmatter naming conventions and creates the required section structure for publishable docs automatically.