← ClaudeAtlas

architecture-diagramminglisted

Use at :architect — what judges actually read in an architecture diagram, and the tier model the three emitters render from.
rogerjeasy/win-hackathon · ★ 0 · AI & Automation · score 60
Install: claude install-skill rogerjeasy/win-hackathon
# What a diagram is for A judge spends seconds on the diagram, not minutes. It has one job: let them place the system before they read a word of prose. Everything below is either evidence for how the corpus actually drew that picture, or the model this plugin's three emitters render it from. ## The corpus Five winning projects, five different diagramming approaches — no two the same: | Project | Approach | |---|---| | Kintwadi (Best Design) | `.drawio` source, an inline Mermaid diagram in `docs/architecture.md`, and a manually-exported `.png` | | Sonar (1st, Million-scale Global) | Inline SVG hand-authored inside a Python script, `generate_pdf.py`, rendered to PDF | | HYPE (Best Technical Implementation) | `.svg` | | Relay (Most Impactful) | `.svg` plus a separately shipped `.png` | | Karma (Second Place, Dynatrace) | ASCII box art, drawn directly in `docs/ARCHITECTURE.md` | **No project in the corpus automated a drawio-to-PNG export.** Kintwadi's `.png` — the only one in the corpus documented as coming from a drawio source — was made by hand: someone opened the drawio file in app.diagrams.net and clicked Export. Relay shipped a separate `.png` too, but not by way of drawio at all. Every other project skipped raster entirely and committed a hand-authored SVG or ASCII format directly. Nothing in the corpus runs a headless renderer, and this plugin doesn't either: it emits Mermaid and SVG, which cover every case a PNG would, and leaves the export step manual exactly where