cartographer
SolidOwn the repo map — configure mapping to THIS repo, wire auto-remap, install semantic extractors, curate authored navigation, and finish through one truthful finalization gate. Cartographer-only.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- jedbjorn
- Repository
- jedbjorn/subfloor
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
wayfinder-cartographer
Build a walkable map of a body of work (a repo, a database/base, a vault, a client-delivery folder, an automation pack) that a newcomer or a cold AI can enter and wander without reading the whole thing. Produces a catalog plus one card per noun, marks live/leftover/ghost, and names what each change hits and the wrong neighbour it does not. Use when the user says "map this system/repo/base/folder", "make a map", "onboard someone to X", "what are the moving parts of X", "help a new person or model understand this", or hands over a large body of work someone will change. NOT for diagnosing why something failed, and never map the methodology itself.
cartographer
Compile survey records into a map — an append-only body of claims plus a mutable, authoritative index that resolves a topic to the current claim, tracks resolution per area, and marks contested findings. Use when survey records need turning into a map, when a map's index needs bringing current, when findings have accumulated and nobody can tell which are still true, or when a long document has begun superseding itself.
map
Codebase orientation for an unfamiliar or large repo — "map this before I work in it." Fans out read-only Explore sub-agents that navigate the code (keyless — grep/glob/read, no embeddings to go stale) along the order that matters: entry points, build/test/lint commands, architecture and key abstractions, conventions and gotchas, test layout. Distills the findings into a lean AGENTS.md at the repo root — the cross-tool standard file many agents auto-load — where every claim points to a real file and nothing survives that isn't load-bearing. Human-in-the-loop: it drafts, you approve, and it never writes or commits into your repo without an explicit yes. Stamps the map with date + commit so /map refresh regenerates only what went stale. Use before working in a repo you or the agent don't know — e.g. "/map", "/map the auth subsystem", "generate an AGENTS.md", "/map refresh". Run it upstream of feature or bugfix; for the end-of-session shipping gate use done.