architecture-diagram

Generate detailed layered architecture diagrams as self-contained HTML artifacts with inline SVG icons, CSS Grid nested container layout, SVG path connection overlays, and color-coded connection legends. Triggers on: "architecture diagram", "infra diagram", "system diagram", "deployment diagram", "network diagram", "topology", "draw architecture", "visualize architecture", "system topology", or any request for visual representation of system components, containment hierarchy, and interconnections. For architecture reviews, audits, critiques, or design assessments, use architecture-reviewer instead.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "architecture-diagram" with this command: npx skills add mathews-tom/praxis-skills/mathews-tom-praxis-skills-architecture-diagram

Architecture Diagram Generator

Produces self-contained .html files: inline SVG icons, CSS Grid nested zones, JS-driven SVG connection overlay with color-coded semantic line types and arrowhead markers. Zero external dependencies.

Workflow

  1. Parse user input → extract: components (with descriptions), containment hierarchy (zones/nesting), connections (with semantic types), and any provider context
  2. Read references/icons.md — select or create icons for each component
  3. Read references/layout-patterns.md — choose topology pattern, set grid-template-columns
  4. Read references/connections.md — define connection array with types, side-forcing, routing
  5. Start from assets/template.html — use its CSS/JS structure as the base
  6. Assemble the HTML:
    • Set {{DIAGRAM_TITLE}}, {{BG_COLOR}}, {{MAX_WIDTH}}
    • Populate {{LEGEND_ITEMS}} — one entry per connection type used
    • Build zone hierarchy as nested div.zone > span.zone-label + div.zone-content
    • Place nodes with data-node-id, each containing: .node-icon (inline SVG), .node-title, .node-desc
    • Populate the connections JS array
    • Apply provider theming if applicable
  7. Output final .html to the working directory or user-specified path

Node construction

Every node must have:

  • Unique data-node-id (semantic: fusion-hcm, edi-adaptor, not node-7)
  • .node-icon with inline SVG from the icon registry (or custom-generated following registry constraints)
  • .node-title — short name (1–3 words, bold)
  • .node-desc — extended description text (protocols, module lists, capabilities). Populate this whenever the user provides detail beyond just a name. This is critical for professional-quality diagrams.

Key structural invariants

  • Every div.zone has exactly one span.zone-label and one div.zone-content
  • Every div.zone-content has explicit style="grid-template-columns: ..."
  • Zone depth class (zone-depth-0 to zone-depth-3) matches actual nesting level
  • All SVG icons are inline inside .node-icon — no external image references
  • Connection overlay SVG with <defs> (arrow markers for each color) sits after the diagram div
  • Connection renderer <script> is last before </body>
  • Legend div sits above the diagram div, containing only types actually used

Connection type selection

Match connection semantics to the appropriate type:

  • realtime (blue solid): REST, SOAP, API calls, synchronous requests, real-time data
  • batch (red dashed): SFTP, file transfers, EDI, scheduled batch jobs, bulk data
  • event (green solid): event-driven triggers, pub-sub, webhooks, callbacks, business events
  • control (orange dashed): management plane, monitoring, config push, admin flows
  • default (blue solid): when semantic type is ambiguous or only one flow type exists

When the user doesn't specify flow semantics, default all connections to default type and omit the legend.

Design defaults

  • Background: #f0ece4 (warm neutral) or #e8eef5 (cool blue-gray) — choose based on provider/context
  • Zone borders: dashed, colored by depth (warm browns → reds)
  • Icons: 44×44px, --icon-color: #3a3a3a (or provider-specific)
  • Node title: 12px bold, node desc: 10.5px regular #555
  • Connections: 2px stroke, curved by default
  • Font: Segoe UI / system-ui stack
  • Max-width: 1400px typical, increase for complex diagrams

Handling ambiguity

  • Infer zone nesting from naming conventions (Region > VPC > Subnet, etc.)
  • Default to default connections and no legend if flow types are unspecified
  • Place management/observability services outside the main data-path zones
  • Use generic icon set and warm-neutral background unless provider is specified
  • Ask for clarification only when component list or topology is fundamentally ambiguous

Error Handling

ProblemCauseFix
assets/template.html missingFile deleted or skill directory incompleteRegenerate from skill defaults: reconstruct the CSS/JS skeleton using the structure documented in this SKILL.md and the reference files
Icon reference not found in references/icons.mdComponent type not in the registryFall back to the generic box icon defined in references/icons.md § Generic Fallback; log the missing icon name in a comment
Connection lines overlap or route through nodesDense graph with auto-routing conflictsAdjust zone layout: increase grid-template-columns spacing, add intermediate waypoint nodes, or use side-forcing attributes from references/connections.md
Playwright render failure during HTML-to-image exportChromium not installed or script errorRun playwright install chromium; check browser console via --headed flag; verify no JS syntax errors in the connection renderer script
Zone nesting exceeds depth-3 stylingArchitecture has more than 4 containment levelsFlatten by combining the deepest two levels into a single zone, or split into two separate diagrams linked by description

References

  • references/icons.md — 28+ SVG icon definitions, custom icon rules, provider color table
  • references/layout-patterns.md — node structure, zone nesting, 5 topology patterns, interior grid guidance, sizing table
  • references/connections.md — connection schema, 6 semantic types with colors, side-forcing, route modes, legend markup
  • assets/template.html — complete HTML skeleton: CSS, legend, zone/node styles, marker defs for all colors, connection renderer JS with auto side-detection

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

rag-auditor

No summary provided by upstream source.

Repository SourceNeeds Review
Security

dependency-audit

No summary provided by upstream source.

Repository SourceNeeds Review
General

manuscript-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

html-presentation

No summary provided by upstream source.

Repository SourceNeeds Review