Produce an interactive diagram using the bundled graph-driven renderer. Treat the
reference's visual language as inspiration; create original code and content.
Keep this file as the invocation entry point. Read the references below on demand;
leave README, CHANGELOG, and meta/MAINTAINERS for maintainers.
Interpret
/network-flow [[ system description ]]
followed by these options:
The slash-command
selects a format. The bundled CLI's
requires an actual path, such as
. The bundled renderer
supports only the defaults above. Reject unsupported values clearly rather than
silently substituting. For measured traffic, read
references/telemetry.md and implement an explicitly
requested adapter separately; never label this simulated renderer as telemetry.
-
Model the system. Extract components, directed connections, source/destination
roles, meaningful scenarios, and failure/recovery branches. Infer routine
presentation choices. Ask only if missing information changes system meaning.
Identify assumptions and label fictional examples. Keep alternative failure
outcomes explicit; do not depict both outcomes as one successful execution.
-
Write graph JSON. Read
references/graph-schema.md.
Reuse the shape in
assets/examples/rag/generated/rag.json
; replace its content for another system.
Attach source provenance to evidence where relevant. Express simulated steps
in order. Limit a diagram to 24 nodes; split larger systems into scoped diagrams.
-
Lay out and validate. Prefer curated wide/medium/narrow positions for complex
graphs; use automatic row placement for small graphs. Read
references/layout.md for geometry and limitations.
Run
python3 <skill-dir>/scripts/validate_graph.py <graph.json>
. Correct invalid
identifiers, endpoints, scenario scopes, and overlapping layout cells first.
-
Render the file. Run:
sh
python3 <skill-dir>/scripts/render.py <graph.json> \
--theme dark-grid --routing orthogonal --mode simulated \
--output <output-dir>/system-flow.html
Pass
--scenarios ingest,answer,retry,all
only when those scenario IDs exist.
Work in the requested project/output directory; never edit the installed
template to create a particular diagram. Do not overwrite unrelated files.
-
Verify actual behavior. Check desktop and mobile browser renders, card text,
attached orthogonal paths, moving packets, scenario captions, pause/resume,
replay, node focus, keyboard clear, and reduced-motion behavior. Read
references/verification.md and use the bundled
browser check when available. Fix failures and rerun relevant checks. If browser
verification is unavailable, disclose that limit; do not claim it passed.
-
Deliver completely. Provide the actual
file through the host's file
mechanism and a concise description of controls. Show an interactive preview
when supported. If the host needs an HTML fragment, extract the body after
generating the standalone file, preserve its scoped CSS and scripts, and keep
the downloadable document as the deliverable. Do not stop at a static image,
Mermaid diagram, unexecuted source snippet, or promised attachment. Never claim
a file is hosted or published unless that separate action succeeded.
assets/examples/rag/generated/rag.json
and its generated
cover ingestion,
retrieval, reranking, context assembly, generation, citation resolution, bounded
retry, and abstention. The handbook quotation is illustrative, not sourced policy.
The retry playback explicitly labels the exhausted path as an alternative outcome.
For the original delivered visual and its exact invocation, use
assets/examples/rag/original/rag_demo.html
and
. These are a preserved
example pair;
assets/examples/rag/generated/rag.json
remains the editable renderer fixture.
The design reference is the interactive architecture graphic in
Vercel's Python announcement.
No Vercel source code, logos, or branded assets are bundled.