feature-diagram

To generate architecture diagrams from a feature inventory, the Skill reads your consolidated feature matrix and renders routes, models, jobs, and UI surfaces into a Mermaid flowchart. It outputs a dedicated markdown file and updates the inventory with a back-link.

A Mermaid flowchart maps HTTP routes and data models by reading the target feature's inventory data and inferring graph edges between components. It organizes these elements into four distinct subgraphs to visualize the feature's architecture.

Yes, you can visualize async jobs and UI screens even when surfaces are missing. The Skill maintains four named subgraphs—Screens, Routes, Models, and Jobs—and automatically populates absent surfaces with placeholder nodes to ensure consistent visuals.

The best way to automate per-feature architectural visualization is running the Skill against a populated feature-inventory and target feature slug. It produces a regenerable markdown file with a traceability footer, ready for linting and future regeneration.

Yes, you need a consolidated feature matrix and a populated feature-inventory before creating per-feature Mermaid diagrams. The Skill relies on this existing inventory data to infer graph edges and accurately map routes, models, jobs, and UI screens.