shine-architecture-diagram

Generate Mermaid graphs or draw.io XML from natural-language system descriptions.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-architecture-diagram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-architecture-diagram
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-architecture-diagram
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-architecture-diagram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate architecture diagrams from natural-language descriptions to accelerate design reviews and documentation.

Core Features & Use Cases

  • Mermaid graph generation from system descriptions including services, databases, external APIs, queues, auth, and observability.
  • draw.io XML output for interactive diagrams with clustering for subsystems and a 15-node limit.
  • Ideal for cloud architecture planning, software system design, and doc generation.

Quick Start

Describe the system you want diagrammed and I will output a Mermaid graph or draw.io XML.

Frequently Asked Questions about shine-architecture-diagram

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

FAQPage Schema
How do I generate architecture diagrams from natural language descriptions?

To generate architecture diagrams from natural language, describe your system's services, databases, APIs, and queues. The tool outputs Mermaid graphs or draw.io XML with clustered sub-systems, enforcing a 15-node limit to keep visualizations readable.

Can I output both Mermaid graphs and draw.io XML for cloud infrastructure design?

Yes, you can output both Mermaid graphs and draw.io XML for cloud infrastructure design. Mermaid is ideal for quick markdown documentation, while draw.io XML provides interactive diagrams with visual clustering for complex sub-systems.

What is the best way to document software architecture with services, queues, and observability?

The best way to document software architecture with services, queues, and observability is through automated diagram generation. Provide a text description of your system components and receive structured Mermaid or draw.io visualizations for design reviews.

Does the generated diagram support clustering for complex sub-systems and external APIs?

Yes, the generated diagram supports clustering for complex sub-systems and external APIs. It automatically groups related services, databases, and observability components, maintaining a strict 15-node limit to ensure the system documentation remains legible.

What are the limitations of generating system diagrams from text descriptions?

A key limitation of generating system diagrams from text descriptions is the enforced 15-node limit. This constraint prevents overly complex visualizations, requiring you to abstract or split larger cloud infrastructure designs into multiple clustered sub-system diagrams.