Aryanutkarsh / SeeCode
git clone https://github.com/Aryanutkarsh/SeeCode.git
v0.6.2 · 3d ago
Animated, explorable diagrams for Claude and other coding agents, from a short JSON spec.
—
stars, 24h
—
stars, 7 days
+690
stars, 30 days · #427
690
★ total
38
forks · 0 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageJavaScript
LicenseMIT
Created2026-10-02 (18d ago)
Last push3d ago
Watchers2
OwnerUser
GitHub topics
agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdata-visualizationdeveloper-toolsdiagramsdiagrams-as-codedrawioflowchartisometricmermaidsequence-diagramsoftware-architecturesvgsystem-designvisualization
Links
README excerpt
Diagrams that move, explain and export themselves. Ask your agent for a diagram. SeeCode turns a short spec into an editorial-quality, animated, explorable diagram: one HTML file you can hover, click and walk through, or export as SVG, PNG, GIF or MP4 for wherever it needs to go. Install · Diagram types · Features · Themes · Import · Export · CLI Exported straight from the diagram. ▶ See the viewer in action : hover trace, focus panel, route journey. ## Install, then describe what you want to see **Claude Code** (recommended: the plugin keeps you on the latest release): [code] **Cursor, Codex, OpenCode and other Agent Skills hosts:** [code] More install options, and how to update. Then ask: [code] Keep going in plain language: *"highlight the payment path"*, *"make it dark"*, *"export it for my slides"*. The first time you use it in a project, SeeCode asks once whether to use your global settings or create project-specific ones. ## 45 diagram types Every type animates its own way (systems trace their flows, sequences play message by message, charts grow), and every type can also be fully static. Click any diagram for the full-size image. Charts take their numbers from a CSV or JSON file, so the data never has to pass through the model. Architecture Components and connections High-level 4–7-box overview for non-engineers Deployment Where things run (hosts, regions) Dependency graph What imports or depends on what Architecture delta What a change adds, removes or alters IT current state Current IT landscape with health status UML class Classes and interfaces ER / data model Entities and cardinality Database schema Tables and FK columns Flowchart Decisions and branches Sequence Messages between actors over time State machine States and transitions Swimlane Who does which step Process Short linear numbered steps Data flow Data moving through stages User journey User steps and emotion curve Timeline Dated events Gantt Work over time Kanban Items by status Story map Backbone and release slices Loop / flywheel Reinforcing cycle or flywheel Medallion Bronze/silver/gold layers Platform integration Sources → integration → platform → serving Access matrix Roles × data access Tree Parent → children Org chart People and teams Nested Containment and scopes Layer stack A stack Venn Overlaps Pyramid / funnel Ranking Quadrant A 2×2 Fishbone Root causes Wardley map Evolution × visibility Exploded view Parts of one thing, isometric Isometric plan A floor or site from above Isometric object Any object, from a description Bar Compare amounts Line Change over time Scatter Two measures Waterfall Running total Treemap Part of whole Heatmap Intensity grid Radar Profile on shared axes Polar Cyclical values Sankey Flow volumes Plus 15 variants: dumbbell, marimekko, slopegraph, bump, streamgraph, ridgeline, bubble, beeswarm, funnel, consultant quadrant,