describe-design

To generate architecture documentation, you can use a Skill that researches your codebase to identify entry points and dependencies, then produces a structured markdown document with Mermaid diagrams and stable code references.

Creating an onboarding guide for a complex software system is best handled by analyzing source code to extract component boundaries and data flow, yielding a clear architectural overview that reduces onboarding time.

To document component interactions and data flow in a feature, research the codebase architecture and compile a structured design document that includes clear explanations and Mermaid diagrams.

Yes, you can automatically generate Mermaid diagrams for your codebase architecture by investigating the source code to map dependencies and component boundaries, which are then rendered into a structured design document.

Yes, this approach works for internal knowledge transfer by turning scattered source code into a durable, human-readable design overview that clearly explains system interactions, configuration, and persistence.

No specific dependencies are required to research a codebase and produce a design document, as the process relies on standard codebase exploration to generate structured markdown with stable file and symbol references.