Skip to content
Back to search

architecture-explorer

MarketplaceWorks with Claude CodeGitHub

A Claude Code skill: an interactive, live architecture map of your repository (layers, API routes, tables, permissions, screens, services), every link traced to its file and line.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lemonadehighway--architecture-mapping/badge.svg)](/listings/lemonadehighway--architecture-mapping)

HTML

<a href="/listings/lemonadehighway--architecture-mapping"><img src="/api/listings/lemonadehighway--architecture-mapping/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need [Claude Code](https://claude.com/claude-code) and Node.js 20 or later.

**As a plugin** (from Claude Code):

/plugin marketplace add LemonadeHighway/Architecture-Mapping
/plugin install architecture-explorer@architecture-explorer

**As a plain skill:** copy `skills/architecture-explorer` into `~/.claude/skills/` (for all your projects) or into a project's `.claude/skills/`.

Then, in any repository, ask Claude something like *"show me the architecture of this project"* or *"open the architecture explorer"*. Claude starts the explorer, opens the map, and can set up a config for your project's own conventions.

**Without Claude:**

node skills/architecture-explorer/explorer/server.mjs --root /path/to/your/repo
node skills/architecture-explorer/explorer/cli.mjs --root /path/to/your/repo

The server prints its address (`http://127.0.0.1:5190` or the next free port). The CLI prints a summary, the coverage table and the findings; `--node <id>` and `--find <text>` answer questions from the terminal.

The explorer has no runtime dependencies. For TypeScript and JavaScript files it uses the TypeScript parser from the scanned project's `node_modules`; if the project has none, run `npm install` once in `skills/architecture-explorer/explorer` (it installs only `typescript`).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines
  1. {
  2. "name": "architecture-explorer",
  3. "owner": { "name": "Zaid Zaatreh" },
  4. "plugins": [
  5. {
  6. "name": "architecture-explorer",
  7. "source": "./",
  8. "description": "An interactive, live architecture map of your repository, with every relationship traced to its source.",
  9. "version": "0.1.0"
  10. }
  11. ]
  12. }
README.md · README · 101 lines
  1. # Architecture Explorer
  2. A Claude Code skill that turns a repository into an interactive, live architecture map: layers, modules, API
  3. routes, database tables, permissions, screens, outside services and the business workflow, with every relationship
  4. traced to the file and line it comes from.
  5. ![Overview of a sample shop](docs/overview.jpg)
  6. Built for people who are building a system and want to *see* it: what calls what, who may call which address, which
  7. tables a feature touches, where a new feature belongs, and what changed. It runs on your computer, reads the code,
  8. and never changes it.
  9. ## What you get
  10. - **Eleven views of one scan:** overview, software architecture, functional modules, code structure, module
  11. dependencies, frontend ↔ backend, API connections, database, business workflow, security & permissions, external
  12. integrations.
  13. - **Explore anything:** double-click a box to see what uses it, what's inside, and what it uses. Click a line to see
  14. the code behind it; every `file:line` opens the source.
  15. - **Honest about certainty:** each relationship is *verified* (a literal fact in the code), *inferred* (a name match
  16. or a convention) or *unresolved*. A Coverage tab compares raw text matches with what was understood and lists
  17. everything left over.
  18. - **Health findings:** addresses that change data with no authorization, sign-in-only writes, frontend calls that
  19. match no route, routes nobody calls, permissions nothing checks, tenant tables without row-level security, secrets
  20. in settings files. Each comes with its places and a ready prompt for Claude Code.
  21. - **Live:** it watches the repository and updates the open page when files change, with git's uncommitted changes
  22. marked.
  23. - **Search and Ask:** find files, routes, tables, permissions; ask "who calls /api/orders" or "which addresses are
  24. open" (index search, no AI, nothing leaves your machine).
  25. ![Security view](docs/security.jpg)
  26. ## What it understands
  27. | Area | Understood |
  28. |---|---|
  29. | C# / ASP.NET Core | Minimal APIs (`MapGet`…, route groups, helper methods that map routes), controllers with attribute routes, `[Authorize]` / `[AllowAnonymous]`, `RequireAuthorization`, `AddPolicy`, `IsInRole`, the fallback policy, DI registrations, handler and constructor injection, project references |
  30. | Data | `.sql` migrations replayed in order (tables, columns, foreign keys, indexes, triggers, row-level security), SQL in C# strings (Dapper, Npgsql, ADO.NET), EF Core `DbSet`s |
  31. | Frontend | TypeScript / JavaScript with `fetch`, `axios`, `api.get(...)` clients and `apiGet`-style helpers matched to server routes; imports with `tsconfig` path aliases; React Router, switch-based routers and Next.js `app/` / `pages/` screens |
  32. | Outside services | URLs in code, and well-known client packages (PostgreSQL, SQL Server, Redis, Stripe, Twilio, SendGrid, AWS, Azure, Auth0, Sentry, OpenAI, ...) |
  33. | Project conventions | Your own permission enum, route guards and permission checks, and your documented business process, through an optional `.architecture-explorer.json` ([reference](skills/architecture-explorer/references/configuration.md)) |
  34. Not modeled yet: EF Core migrations written in C#, JavaScript backends (Express, Next.js API routes), GraphQL, gRPC.
  35. C# is read by a C#-aware lexer, not compiled, so links between C# types are name matches and marked inferred.
  36. ## Install
  37. You need [Claude Code](https://claude.com/claude-code) and Node.js 20 or later.
  38. **As a plugin** (from Claude Code):
  39. ```
  40. /plugin marketplace add LemonadeHighway/Architecture-Mapping
  41. /plugin install architecture-explorer@architecture-explorer
  42. ```
  43. **As a plain skill:** copy `skills/architecture-explorer` into `~/.claude/skills/` (for all your projects) or into a
  44. project's `.claude/skills/`.
  45. Then, in any repository, ask Claude something like *"show me the architecture of this project"* or *"open the
  46. architecture explorer"*. Claude starts the explorer, opens the map, and can set up a config for your project's own
  47. conventions.
  48. **Without Claude:**
  49. ```bash
  50. node skills/architecture-explorer/explorer/server.mjs --root /path/to/your/repo
  51. ```
  52. ```bash
  53. node skills/architecture-explorer/explorer/cli.mjs --root /path/to/your/repo
  54. ```
  55. The server prints its address (`http://127.0.0.1:5190` or the next free port). The CLI prints a summary, the coverage
  56. table and the findings; `--node <id>` and `--find <text>` answer questions from the terminal.
  57. The explorer has no runtime dependencies. For TypeScript and JavaScript files it uses the TypeScript parser from the
  58. scanned project's `node_modules`; if the project has none, run `npm install` once in
  59. `skills/architecture-explorer/explorer` (it installs only `typescript`).
  60. ## Privacy and safety
  61. - Listens on 127.0.0.1 only and refuses requests for any other host name.
  62. - Read-only: it never writes to the repository; it runs only read-only git commands (`status`, `log`, `rev-parse`).
  63. - Only files the scan indexed can be opened from the page; secret-looking values in JSON settings are masked.
  64. - No network calls, no telemetry, no AI in the page.
  65. ## Develop
  66. ```bash
  67. cd skills/architecture-explorer/explorer
  68. npm install
  69. npm test
  70. ```
  71. The tests scan a small sample shop (`test/make-fixture.mjs`) end to end, check each scanner on small inputs, and
  72. start the real server to prove that a file change reaches the open page.
  73. ## License
  74. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.