architect-diagram

The skill generates grounded Mermaid diagrams by reading your repository first, anchoring names, boundaries, and relationships to real code and documentation. It routes to the correct notation like flowchart, sequence, state, or ER based on your specific system design intent.

The best way to document cloud deployment topologies is using C4-style Mermaid diagrams with correct trust boundaries and edge labels. The skill handles AWS, Azure, GCP, and managed agent platforms to produce compact, readable topology maps for your architecture documentation.

Yes, you can reverse-engineer a repository into sequence diagrams. The skill reads your codebase to map real system interactions and flows into grounded Mermaid sequence diagrams, ensuring correct notation routing and one-screen readability without fabricating entity names.

Yes, notation routing automatically chooses between flowchart, sequence, state, ER, or C4-style Mermaid output based on your stated intent. This ensures the generated diagram accurately represents the specific system structure, lifecycle, or entity relationships you need documented.

A limitation when generating architecture diagrams for complex agentic systems is maintaining one-screen readability without fabricated names. The skill requires accurate repository references to establish visible trust boundaries and labeled relationships, preventing ungrounded or overly cluttered Mermaid outputs.