cartograph
Cartograph
Extract a structural map of any TypeScript/JS web app: surfaces, features, entities, relationships, operations, flows, and compartments. Four orthogonal axes — surfaces are where you go (pages/entry points), features are what you can do (standalone capabilities), entities are what the app works with (data), and compartments are how the code is organized (logical file groupings that bridge product concepts to the underlying codebase).
Workflow
The workflow runs in 5 waves plus a parallel health pass (Wave 3.5). Within each wave, spawn the listed agents in parallel, wait for all of them to finish, then move to the next wave. Each agent should return its results as a JSON array (or arrays) matching the schema in references/json-schema.md. Between waves, you are the orchestrator — collect agent outputs and pass them as context to the next wave's agents.
Wave 0: Discover Codebase Structure
Run this yourself (no agent needed — it's fast and every later agent needs the results).
- Read
package.jsonfor project name and dependencies (framework detection) - Glob for key structural files:
- Schema:
**/*.prisma,**/schema.*,**/models/** - Routes/Pages:
app/**/page.{tsx,ts,jsx,js},app/api/**/*.{ts,js},pages/**/*.{tsx,ts} - Server actions: grep for
"use server"
- Schema:
More from ilamanov/skills
spec-builder
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
23pr
Commit changes and create or update a pull request following project standards. Use when the user wants to commit work, create a PR, update an existing PR, or use the /pr command.
14reimplement-branch
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when the user wants to clean up messy commits, create a tutorial-style commit history, or prepare a branch for review with logical, self-contained commits. Triggers on requests like "clean up my commits", "reimplement this branch", "create a clean history", or "make my commits reviewable".
12deslop
Remove AI-generated code slop and clean up code style
10compile-conversation-into-doc
Turn long, messy AI chat conversations into clear, durable, and easily scannable reference documents that humans can reliably return to weeks or months later.
9review-bug-fixer
Fix valid code review findings from one or more review markdown files. Use when the user has review files (e.g., review1.md, review2.md) containing code review findings, issues, or suggestions and wants to fix the valid ones in the current branch. Triggers on requests like "fix review findings", "fix issues from review", "apply code review fixes", or any mention of fixing bugs/issues from review markdown files.
8