Architecture Diagram Skill

"How does the system fit together?" is best answered with a picture. This skill turns a described system into a clean Mermaid architecture diagram — clients, services, data stores, and third parties, grouped into logical layers with labelled connections (sync vs async, protocols) — not an undifferentiated blob of boxes.

Required Inputs

Ask for these only if they aren't already provided:

• The components — services, apps, databases, queues, external APIs.
• How they connect — who calls whom; sync (HTTP/gRPC) vs async (queue/event); data flow direction.
• Logical groupings — frontend / backend / data / third-party, or by team/domain.
• Focus — the whole system or one slice (e.g. just the checkout path).

Output Format

[System name] — architecture