| name | architecture-diagram |
| description | Dark-themed SVG architecture/cloud/infra diagrams as HTML. |
| allowed-tools | ["write_file","read_file"] |
| enabled | true |
| related-skills | ["concept-diagrams"] |
| license | MIT |
| author | Adapted from hermes-agent (Nous Research, MIT); Cocoon AI |
Architecture Diagram
Overview
Generate professional, dark-themed technical architecture diagrams as
standalone HTML files with inline SVG graphics. No external tools, no API keys,
no rendering libraries — just write the HTML file and open it in a browser.
Scope
Best suited for:
- Software system architecture (frontend / backend / database layers)
- Cloud infrastructure (VPC, regions, subnets, managed services)
- Microservice / service-mesh topology
- Database + API map, deployment diagrams
- Anything with a tech-infra subject that fits a dark, grid-backed aesthetic
Look elsewhere first for:
- Physics, chemistry, math, biology → use
concept-diagrams
- Floor plans, educational visuals → use
concept-diagrams
- Hand-drawn sketches → use excalidraw
Workflow
- User describes their system architecture (components, connections,
technologies)
- Generate the HTML file following the design system below
- Save with
write_file to a .html file
- User opens in any browser — works offline, no dependencies
write_file("architecture.html", "<full HTML with inline SVG + CSS>")
Output Location
./[project-name]-architecture.html
Design System
Aesthetic
- Dark background: deep navy or black (#0a0a1a, #111)
- Grid pattern: subtle dot or line grid in background
- Neon accents: luminous colors for different component types
- Monospace labels: for technical authenticity
- Rounded corners: on boxes (rx=6)
- Glow effects: subtle box-shadow on key components
Color Palette
:root {
--bg: #0a0a1a;
--grid: #1a1a2e;
--c-frontend: #00D9FF;
--c-backend: #50C878;
--c-database: #F5A623;
--c-external: #C4A7E7;
--c-queue: #FF6B6B;
--c-cache: #FFD700;
--text: #E0E0E0;
--text-dim: #888;
--border: #333;
}
SVG Template
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Architecture Diagram</title>
<style>
body {
margin: 0; padding: 40px;
background: var(--bg);
background-image: radial-gradient(circle, var(--grid) 1px, transparent 1px);
background-size: 30px 30px;
}
svg { display: block; margin: 0 auto; }
.component {
stroke-width: 2; rx: 6; ry: 6;
fill-opacity: 0.1;
}
.label {
font-family: 'SF Mono', 'Fira Code', monospace;
font-size: 13px; fill: var(--text);
}
.label-type {
font-size: 10px; fill: var(--text-dim);
: uppercase; : ;
}
{
: (--text-dim); : ;
: none; : ;
: ();
}
Web App
Frontend
API Server
Backend
PostgreSQL
Database
Diagram Patterns
Layered Architecture
- Frontend (top) → Backend (middle) → Database (bottom)
- Horizontal layers with vertical connections
Microservice Topology
- Central API gateway + surrounding services
- Bidirectional connections for sync, one-way for async
Cloud Infrastructure
- VPC as a large container box
- Subnets as inner boxes
- Managed services as icons (S3, Lambda, RDS)
Data Flow
- Left-to-right flow
- Different line styles for sync (solid) vs async (dashed)
Pitfalls
- Too many components: keep to 5-10 boxes max. More = unreadable.
Split into multiple diagrams if needed.
- Crossing lines: route connections to minimize crossings. Use right-angle
paths.
- No legend: if using color-coded component types, include a legend.
- Font sizing: labels must be readable. 13px minimum for component names.