What problem does it solve?
Understanding and documenting the architecture of a large Go codebase like Radius is slow and error-prone when done manually, and diagrams drawn from memory quickly drift from the actual code. This Skill traces real call chains, packages, and types in the source to produce accurate architecture explanations and Mermaid diagrams.
Core Features & Use Cases
- Code-grounded diagram generation: Produces Mermaid flowcharts, sequence diagrams, class diagrams, ER diagrams, and state diagrams where every node maps to a real package, type, or function in the code.
- Architecture explanation and Q&A: Explains how subsystems work in plain language, answers architecture questions, and onboards new contributors to the Radius control plane, resource providers, and recipes engine.
- Improvement suggestions: Identifies pain points such as coupling and circular dependencies, then presents current-state versus proposed-state diagrams with trade-off analysis.
- Use Case: Ask how a deployment request flows through the Radius Universal Control Plane, and receive a sequence diagram tracing the actual frontend handler, ARM RPC controller, and async backend, plus a prose walkthrough with file references.
Quick Start
Ask the assistant to document the architecture of a Radius subsystem, for example: show me the request flow when a user deploys an application through the UCP.
