What it does
google maps for vibecoders.
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/quinnaho-claudemap)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one claudemap | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | QuinnAho | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 295 | 468,733 | 234,332 | 150,287 | 144,566 |
| Last code change | Apr 21, 2026 | Nov 19, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by QuinnAho that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodex
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account QuinnAho (person), 3 years old
- Use and upkeep
★ 295 stars, few users so far · code last changed Apr 21, 2026
- Any scripts?
60 scripts that can run on a computer: commands/create-map.js, commands/open-claudemap.js, commands/refresh.js, commands/setup-claudemap.js and 56 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit c0a9b93 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Files are byte-for-byte the same as on GitHub at commit c0a9b93 · View on GitHub ↗
60 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
Look inside before downloading
All 65 files · 296 KB
SKILL.md7 KBcommands/create-map.js11 KBcommands/open-claudemap.js4 KBcommands/refresh.js11 KBcommands/setup-claudemap.js9 KBcommands/show.js19 KBcommands/snapshot.js1 KBlib/active-map.js1 KBlib/cache.js2 KBlib/command-harness/enrichment-io.js1 KBlib/command-harness/log.js1 KBlib/command-harness/parse-args.js5 KBlib/command-harness/project-root.js1 KBlib/command-harness/render-slash-template.js2 KBlib/command-harness/run-command.js5 KBlib/command-harness/slash-only-descriptors.js2 KBlib/command-harness/with-mcp.js1 KBlib/contracts/errors.js3 KBlib/contracts/graph-sources.js1 KBlib/contracts/index.js1 KBlib/contracts/paths.js11 KBlib/contracts/paths.test.js11 KBlib/contracts/presentation.js1 KBlib/contracts/schemas/cache.js1 KBlib/contracts/schemas/graph.js1 KBlib/contracts/schemas/index.js3 KBlib/contracts/schemas/install-record.js2 KBlib/contracts/schemas/manifest.js1 KBlib/contracts/schemas/runtime-envelope.js1 KBlib/contracts/schemas/schemas.test.js11 KBlib/contracts/schemas/shared.js2 KBlib/contracts/versions.js4 KBlib/contracts/versions.test.js9 KBlib/differ.js3 KBlib/differ.test.js12 KBlib/enrichment.js1 KBlib/enrichment/enrichment.test.js11 KBlib/enrichment/graph-validation.js2 KBlib/enrichment/health.js2 KBlib/enrichment/icons.js1 KBlib/enrichment/index.js8 KBlib/enrichment/prompts.js2 KBlib/enrichment/source-priority.js2 KBlib/file-walker.js7 KBlib/import-resolution.js4 KBlib/launcher.js2 KBlib/manifest/fingerprint.js3 KBlib/manifest/index.js2 KBlib/manifest/io.js2 KBlib/manifest/migrations.js2 KBlib/manifest/normalize.js3 KBlib/manifest/scope-resolution.js3 KBlib/manifest/scope-resolution.test.js11 KBlib/map-manifest.js2 KBlib/mcp-client.js24 KBlib/runtime-location.js4 KBlib/runtime-location.test.js4 KBlib/runtime-paths.js3 KBlib/scoped-map.js7 KBlib/show-helpers.test.js8 KBpackage.json1 KBprompts/enrichment.txt5 KBprompts/scoped-enrichment.txt5 KBvitest.config.js1 KBLICENSE1 KB
Download claudemap-runtime.zip
Checking the commands · copy buttons appear once they pass
Open Skills on claude.ai and upload
+Create skillUpload a skillpick claudemap-runtime.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /skill or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /skill or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the claudemap-runtime folder at ~/.agents/skills/claudemap-runtime
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick skill
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick skill
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
7,596 characters · Open the full file on GitHub
---
name: claudemap-runtime
description: Internal ClaudeMap runtime for turning a repository into a live architecture map and driving that map during walkthroughs. Prefer the public commands in .claude/commands for normal use.
---
ClaudeMap is a repo-to-architecture-map workflow.
High-level model:
- snapshot the repository
- ask `@claudemap-architect` to turn that snapshot into a detailed, human-legible graph
- render the graph in the bundled ClaudeMap UI
- keep the graph and presentation state updated as the user explores the codebase
Public commands:
- `/setup-claudemap`: build or rebuild the map for the current repository
- `/open-claudemap`: reopen the existing UI without rebuilding
- `/create-map`: create or refresh a scoped subsystem map from the current root graph
- `/refresh`: update the graph after code changes
- `/explain`: run a guided walkthrough through the live map
- `/show`: direct the live map for highlights, focus, presentation, and flows
If this skill is invoked directly, default to the setup workflow.
Target repository:
- If the user passed an argument to the invoked skill command, use `$ARGUMENTS` as the project root.
- If no argument was passed, use the current working directory.
Execution rules:
1. Resolve the bundled ClaudeMap workspace from `${CLAUDE_SKILL_DIR}`.
2. Generate a raw repo snapshot by running `${CLAUDE_SKILL_DIR}/skill/commands/snapshot.js` for the target project root.
3. Read `${CLAUDE_SKILL_DIR}/skill/prompts/enrichment.txt`.
4. Use the `@claudemap-architect` subagent explicitly. Give it:
- the raw snapshot JSON
- the graph schema contract from the enrichment prompt
- instructions to return only valid graph JSON
- instructions to optimize for a detailed graph with intuitive human grouping
5. **Wait for the subagent Task call to fully return**, then save the returned JSON to `${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json`. Do not run the setup JS command until after this file has been written with non-empty valid graph JSON. Do not run setup in parallel with the subagent call.
6. Run `${CLAUDE_SKILL_DIR}/skill/commands/setup-claudemap.js` for the target project root with `--enrichment-file ${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json`. The setup command is strict: if the file is missing, empty, or unparseable it will exit non-zero and refuse to render a heuristic graph. Do not retry setup without fixing the enrichment file first.
7. Add `--force-refresh` only when the user explicitly asks for a fresh rebuild.
8. If the subagent fails to return valid JSON after two attempts, tell the user the architect pass failed and stop. Do not silently rerun setup without `--enrichment-file` — that would render a heuristic graph and pollute the cache. The user should rerun `/setup-claudemap` once the architect issue is resolved.
9. Let the bundled launcher start the app unless the user explicitly asks not to.
10. Summarize the analyzed file count, system count, graph source, render transport, and app readiness. Runtime graph outputs land in `${CLAUDE_SKILL_DIR}/app/public/graph/` (served by the bundled Vite app as `/graph/*`).
11. End the graph-generation flow with a short feedback prompt such as: `Does this map look right, or should I refine it?`
12. If the user says the map is good, stop there.
13. If the user asks for refinement, reuse the current target project's `claudemap-cache.json` graph and file snapshot as context when available instead of starting from a blank prompt again.
14. For refinement passes, send the existing graph plus the user's requested changes back through `@claudemap-architect`, save the refined JSON to `${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json`, and run `${CLAUDE_SKILL_DIR}/skill/commands/refresh.js` with `--enrichment-file` so the graph iterates in place.
15. After the refined graph renders, ask the same short feedback prompt again.
`/create-map` runs an architect-first scoped pipeline:
1. Resolve the target scope from the user's request (either a scope JSON payload copied from the UI, or a natural language description of a subsystem the architect should locate in the root graph).
2. Read `${CLAUDE_SKILL_DIR}/skill/prompts/scoped-enrichment.txt`. This is a dedicated scoped prompt — do not reuse the root enrichment prompt.
3. Build a scoped snapshot by filtering the root graph's file list to the files inside the target subsystem. Include any prior scoped graph from the target map's `cachePath` when one exists so the architect can refine rather than rebuild.
4. Call the `@claudemap-architect` subagent with the scoped snapshot, the scoped prompt, and any user instructions. Instruct it to emit a richer internal breakdown (2-6 internal subsystems, tighter edges, function nodes welcome) and to decide between edit-in-place and rebuild based on the intent of the request.
5. Save the returned JSON to `${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json` and run `${CLAUDE_SKILL_DIR}/skill/commands/create-map.js` with `--enrichment-file` (plus `--scope-json` and optional `--instructions`). The command deletes the tmp file after it reads it.
6. If the architect pass fails, the command can still fall back to `buildScopedGraphFromRoot` by running without `--enrichment-file`, but warn the user the scoped map will be a plain filter view and suggest rerunning with architect enrichment for richer grouping.
7. After the scoped map renders, ask the same short feedback prompt (`Does this map look right, or should I refine it?`).
8. If the user asks for refinement, reuse the scoped map's own cache as prior graph context (via `buildScopedSnapshot`'s `priorGraph` option) and rerun the architect. Save the refined JSON to the tmp file and rerun `create-map.js` with the same `--scope-json` payload plus `--enrichment-file`.
9. After the refined scoped graph renders, ask the same short feedback prompt again.
`/refresh` is change-aware for scoped maps:
- The root graph is always diffed against the cached snapshot.
- For each scoped map, if none of its files were in the diff and its cached graph was produced by the architect (`meta.source === 'claude-scoped'`), the scoped map is preserved untouched — no rebuild, no filter fallback.
- If the scoped map's files were touched, it is rebuilt from the updated root graph filter and marked `needsRebuild: true` so the next `/create-map` pass knows to rerun the architect for that scope.
- If a scope can no longer be resolved in the new root graph, it is marked `stale: true` and `needsRebuild: true` and left for the user to confirm.
Important details:
- The bundled runtime lives inside this skill directory, so keep all paths anchored to `${CLAUDE_SKILL_DIR}`.
- `/setup-claudemap` should treat the `@claudemap-architect` path as the primary path, not an optional extra.
- The packaged project includes a `claudemap-architect` subagent in `.claude/agents/` for system identification, graph refinement, and human-first graph restructuring.
- If a cached Claude-authored graph already exists, do not replace it with a heuristic regeneration unless the user explicitly asks for `--force-refresh`.
- If the user only wants to reopen the existing map UI, use `/open-claudemap` instead of rerunning setup.
- Follow-up refreshes should use the `/refresh` command shipped in `.claude/commands/refresh.md`.
- Graph refinements should prefer `${CLAUDE_SKILL_DIR}/skill/commands/refresh.js --enrichment-file ...` over rerunning setup so the current graph context is reused.
- `/show` should be treated as a presentation-direction command, not just a low-level transport wrapper.
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 295
- Maker
- QuinnAho
- License
- MIT
- Last code change
- Apr 21, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- anthropic, claude, claude-code, claude-skills, code-visualization-tool, developer-tools, mcp, model-context-protocol, npm-cli, open-source, react, software-architecture