architecture-diagrams

Generate Mermaid, PlantUML, and C4 architecture diagrams for system design documentation.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill architecture-diagrams-luizedupp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-diagrams
Source: https://github.com/LuizEduPP/skills/tree/main/architecture-diagrams
Command: npx skills add https://github.com/LuizEduPP/skills --skill architecture-diagrams-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Large systems rely on diagrams to explain architecture, but manually sketching them can lead to inconsistent notation and outdated documentation. This Skill ensures diagrams stay aligned with technical models by guiding the use of Mermaid, PlantUML, and C4 code-based formats so the visual story matches implementation.

Core Features & Use Cases

  • Code-first Diagramming: Provide Mermaid, PlantUML, and C4 instructions for context, component, deployment, and sequence views so diagrams can be version-controlled and updated alongside code.
  • Reference Library: Use the pre-built reference guides for system, component, data flow, sequence, and deployment diagrams to adapt best practices quickly.
  • Use Case: Document a new microservices feature by outlining the API gateway, services, data stores, and messaging flows in multiple diagram types to share with stakeholders.

Quick Start

Ask for a Mermaid system context diagram that shows your client, API gateway, services, and data layers.

Frequently Asked Questions about architecture-diagrams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture diagrams for system design documentation?

Generate architecture diagrams using text-based Mermaid, PlantUML, and C4 notations to describe components, data flows, and deployments. This approach ensures your visual documentation stays version-controlled and aligned with technical models alongside code.

What is the best way to document microservices architecture with code?

Documenting microservices architecture with code involves using Mermaid, PlantUML, and C4 notations to outline API gateways, services, data stores, and messaging flows. This ensures consistent notation across component, context, and sequence views for stakeholders.

Can I use Mermaid and PlantUML for deployment planning and data flow visualization?

Yes, Mermaid and PlantUML support deployment planning and data flow visualization through code-based formats. Pre-built reference guides help adapt these diagrams quickly to map out system components and technical workflows.

How do I keep architecture diagrams consistent and updated alongside code?

Keep architecture diagrams updated by generating them through text-based code formats like Mermaid and PlantUML. This code-first diagramming method allows diagrams to be version-controlled and modified directly within your engineering documentation workflows.

Does this approach support the C4 model for system context diagrams?

Yes, the C4 model is fully supported for creating system context diagrams. You can use C4 notations along with Mermaid and PlantUML to visualize clients, API gateways, service layers, and data stores in your system design.

When should I use code-based diagrams instead of manual sketching for system design?

Use code-based diagrams instead of manual sketching when documenting large systems to prevent inconsistent notation and outdated documentation. Text-based formats ensure your visual story accurately matches the technical implementation.