Common architecture diagramming

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/common-architecture-diagramming

Standards for creating clear, effective, and formalized software architecture diagrams (C4, UML). (triggers: ARCHITECTURE.md, **/*.mermaid, **/*.drawio, diagram, architecture, c4, system design, mermaid)From its SKILL.md

Install

npx -y skills add ComeOnOliver/skillshub --skill common-architecture-diagramming

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.6 KB, 338 tokens by cl100k_base, as published. Nobody here has run it

Architecture Diagramming Standard

Priority: P1 (Standard)

Guidelines

Use C4 Model: Context->Container->Component->Code.
Audience-Centric: Tailor abstraction (Execs vs. Devs).
Select Type: Sequence (Protocol), ERD (Data), State (Lifecycle), Cloud (Infra). See Selection
Explicit Labels: Label every arrow (e.g., "Uses", "HTTPS").
Consistent Notation: Cylinders=DB, Rectangles=Systems, Dashed=Async.
Metadata: Title, Date, Version, Author.
Legend Mandatory: Define all shapes/colors/styles.
Direction: graph LR (Flow) or graph TD (Hierarchy).
Deployment: Map containers to infrastructure.
Governance: CRITICAL: Review best-practices.md before starting.

Anti-Patterns

Mixed Levels: DB columns in System Context.
Unlabeled Arrows: Ambiguous relations.
Mystery Shapes: Undefined in Legend.
Dead Ends: Unconnected nodes.
Clutter: >20 nodes/diagram.
Acronyms: Undefined abbreviations.

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.