Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

sysmap-to-miro

Release License: MIT Stars

Turn a codebase or system description into editable Miro components — shapes, connectors, and frames you can move and edit, not a screenshot. Choose your icon set (AWS · GCP · Azure · custom). Built on archify.

Most "diagram → Miro" flows drop a flat image on the board. sysmap-to-miro materializes the structure: archify builds and validates a typed system map (components, connections, boundaries, with geometry), and this skill converts that IR into native Miro objects you can actually edit.

A Miro board produced by sysmap-to-miro: a serverless URL shortener with AWS icons, connectors, and titled white zones

The url-shortener example, materialized on a Miro board — AWS icons, labelled connectors, and boundaries as titled zones. Everything is a real, editable Miro object.

Install

npx skills add songstack/sysmap-to-miro

…or as a Claude Code plugin:

/plugin marketplace add songstack/sysmap-to-miro
/plugin install sysmap-to-miro@songstack-plugins

Then restart your agent.

Requirements

  • The archify skill (to generate the IR) — or an existing archify *.architecture.json.
  • A connected Miro MCP (/mcp → authenticate claude.ai Miro).
  • Node ≥ 18.

Use

Ask your agent:

  • "Put a system map of this repo on a Miro board."
  • "Turn docs/architecture.architecture.json into an editable Miro board with AWS icons."
  • "Editable architecture on Miro, GCP icons."

Under the hood:

# deterministic: archify IR -> neutral board plan (frames + nodes + connectors)
node bin/ir-to-miro.mjs path/to/system.architecture.json --iconset aws

The skill then creates the board and materializes the plan via the Miro MCP (layout_create for native shapes/connectors/frames; image_create per node for provider icons).

Icon sets

--iconset On the board
none (default) Native Miro shapes — fully editable, no provider icons
aws / gcp / azure Official provider icons per component + native connectors
custom Your own icons — edit icons/map.json

The type→icon mapping is in icons/map.json; swap --iconset to re-render the same map in any set.

Icon sets

Pass --iconset aws | gcp | azure | custom | none. The same system map renders in whichever provider's icons you choose; none gives plain, fully-editable Miro shapes.

The same five services — API, compute, database, messaging, storage — shown in AWS, GCP, and Azure icons

Icons resolve from each node's label/sublabel (verified against mingrammer/diagrams); unknown or third-party nodes fall back to a neutral glyph.

How it works

  1. archify → validated *.architecture.json (components/connections/boundaries + geometry).
  2. bin/ir-to-miro.mjs → neutral board plan (JSON).
  3. Miro MCPboard_create + layout_create (+ image_create for icons).

archify draws no icons itself — the icon sets live in this skill's render step.

Examples

Four worked, invented system maps in examples/: url-shortener (AWS), ecommerce-checkout (AWS), and its GCP and Azure twins — the identical flow in three icon sets. Each ships with its input IR and the converted board plan; walkthrough in examples/README.md.

The same checkout, rendered on GCP and Azure:

GCP e-commerce checkout on a Miro board Azure e-commerce checkout on a Miro board

node bin/ir-to-miro.mjs examples/ecommerce-checkout-gcp.architecture.json   --iconset gcp
node bin/ir-to-miro.mjs examples/ecommerce-checkout-azure.architecture.json --iconset azure

License

MIT — see LICENSE.

About

Turn a codebase or system map into editable Miro objects — AWS/GCP/Azure icons, connectors, and titled zones. Built on archify.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages