document-recipe

Automating recipe documentation involves executing a four-phase process: pattern extraction, source analysis, drafting, and a conformance check. This workflow analyzes existing TypeScript sources and recipe docs to generate publication-ready markdown files.

Yes, you can generate markdown documentation for a standalone recipe without prior artifacts. The documentation workflow runs independently against an existing recipe, extracting patterns and analyzing sources to produce a complete, conformance-checked final document.

Pattern extraction for component composables documentation works by auto-selecting reference pages based on color patterns. It matches Full patterns to badge.md, Container to card.md, and Minimal to spinner.md to ensure draft alignment with existing recipe formats.

The best way to ensure conformance in Styleframe recipe documentation is through an automated four-phase workflow. The final conformance check phase validates the drafted markdown against extracted patterns and reference pages before writing the output file.

The automated documentation workflow writes the final markdown file to a specific composables directory. The generated output is saved as apps/docs/content/docs/04.components/02.composables/<nn>.<name>.md within your project structure.

Yes, the recipe documentation process supports both standalone recipes and recipe chains. It executes the pattern extraction and source analysis phases across the entire chain, ensuring all linked recipes receive consistent, publication-ready documentation.