architecture-map

Build or update an interactive isometric map of a repository's architecture — buildings sized by real measurements, neighborhoods by subsystem, animated flows tracing actual call paths, and a drift counter that fails CI when the map falls behind the code. Use when someone wants to see, explain, or onboard people to how a codebase fits together, or asks for an architecture diagram, system map, codebase overview, or "show me how this repo works". Adapts to the repo's design system; re-run to refresh.

Try your first task

Inspect a repository for an architecture-map first pass

Start a fresh conversation. Replace the highlighted placeholders.

Use the architecture-map skill to inspect [repository path]. As a small first pass, report the detected framework and router, design tokens, dark-mode mechanism, test runner, and package manager, then briefly identify the real subsystems and call paths that an architecture map should represent. Do not modify files yet.

Required inputs

Repository path, replacing [repository path]

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

218 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗