groma.md
or
↑↓ Navigate↵ OpenEsc Close
ThemeAuto
Help

Reading the map

Islands are systems, slabs are containers, and buildings are components. Round buildings are actors; pills are external systems. Hatched zones group components.

Solid means existing; dashed means draft. Arrows show relationships from source to target.

Building sizes

Floors: source files, grouped into 1–5 floors.
Height: lines of code.
Width: files that depend on it.
Depth: files it depends on.
Patterns: file extensions.

Sizes are relative to the project. Shared floors use the largest measurements; lower floors widen to support those above.

How Groma works

Architecture lives in Markdown. Scans update code evidence; people and agents curate its meaning. Select a component → How it’s built to inspect its files.

Map

Pan
Drag or scroll
Zoom
Pinch or Cmd/Ctrl + scroll
Zoom in or out
+ −
Fit map
0
Clear selection
Esc

Search

Open search
/ or Cmd/Ctrl K
Preview result
↑ ↓
Open result
Enter
Cancel search
Esc

View

Map only
F1
Layers
F2
Map debug
F3

In layers

Orbit
Drag
Pan
Shift + drag
Info
groma.md

Your software architecture as Markdown in Git, and one C4 map you can explore. Groma connects source evidence with the responsibilities and relationships described by people and coding agents.

Groma repository

Runtime libraries

  • @clack/core1.5.1MIT
  • @clack/prompts1.8.1MIT
  • @comark/html0.7.0MIT License
  • @opentui/core0.5.12MIT
  • @parcel/watcher2.6.0MIT
  • @resvg/resvg-wasm2.6.2MPL-2.0
  • comark0.7.0MIT
  • commander15.0.0MIT
  • diff9.0.0BSD-3-Clause
  • fuse.js7.5.0Apache-2.0
  • ignore7.0.10MIT

Development tools

  • @biomejs/biome2.5.14MIT OR Apache-2.0
  • @types/bun1.4.2MIT
  • @types/node26.6.2MIT
  • tsx4.23.15MIT
  • typescript7.1.0-dev.20260924.1Apache-2.0
Hierarchy
●Actor■System
▱Container▪Component

Groma.md

First scan

Ask your coding agent to curate this architecture.

Source scanning uses the plugins selected for this project.