ProvenMap Code

Plugin pmap-code from marketplace provenmap in provenmap/pmap-claude. Commands read from the repo's manifest — today.

Skills (22)

• api-aspect-extraction

  Extracts a repository's API surface (endpoints, protocols, auth, params) into an ApiSurfacePayload for /aspects --api. Use when extracting the api.surface aspect. Reads OpenAPI specs, NestJS/Express controllers, tRPC routers, or GraphQL SDL — never calls the endpoints.

• archetype-analysis

  Heuristics for identifying when a codebase needs a NEW archetype on the server, or when an EXISTING archetype is being stretched/misapplied/duplicated. Used by /analyze-archetypes, and by /analyze when recording the archetype gaps it hit. Defines what makes a good proposal, what to avoid, and how to

• archetype-attributes

  The archetype field contract — which node/edge properties a codebase may fill, which belong to the architect, and how a value reaches the board. Use when authoring board nodes with `attributes`, when a sync reports dropped attribute values, or when deciding whether a property can be evidenced from c

• authz-aspect-extraction

  Extracts a repository's authorization model (roles, resource types, permissions, policies) into an AuthzRegistryPayload for /aspects --aspect authz.registry. Use when extracting the authz.registry aspect. Reads CASL rule definitions, Cerbos policy YAML, OPA Rego policies, Oso Polar files, AWS IAM po

• board-styling

  Author a styling plan for an analyzed board — deterministic signals, model judgment, offline validation. Use when /analyze finishes a board, when running /restyle, or when the user asks to beautify a board or diagram. Covers composition, size presets and icons, and the sparing use of semantic tokens

• pmap-sync

  Bundled Node.js CLI scripts for syncing codebase analysis to the ProvenMap Claude Code Plugin API. Provides pmap-sync.js for smart diff-based sync, pmap-changes.js for reading git history into change periods, pmap-archetypes.js for server archetype caching, pmap-boards.js for board management, and p

• clients-aspect-extraction

  Extracts a repository's outbound service calls (typed HTTP clients, gRPC clients, service-discovery addresses) into an ApiClientsPayload for /aspects --aspect api.clients. Use when extracting the api.clients aspect. Reads .NET AddHttpClient/AddGrpcClient registrations, Aspire WithReference, Refit, f

• codebase-analysis

  Analyzes codebase architecture across multiple languages to extract components, relationships, and tech stacks for C4-style visualization. Use when user asks to "analyze codebase structure", "detect tech stack", "find components", "identify frameworks", "map architecture", or "analyze monorepo". Sup

• db-aspect-extraction

  Extracts a repository's database schema (tables, columns, foreign keys, indexes) into a DatabaseSchemaPayload for /aspects --db. Use when extracting the database.schema aspect. Reads Drizzle, Prisma, TypeORM, SQLAlchemy, raw SQL migrations, or a committed pg_dump — never a live database.

• discover-authoring

  How /discover turns a scored graph reading into insights and context boards worth showing — the plan and its menu, the recommended set, the briefs, the authoring agents, the push order and the report. Use when running /discover, when authoring one discover brief, or when reading a discover plan or l

• event-aspect-extraction

  Extracts a repository's event/messaging catalog (channels, event types, subscriptions) into an EventCatalogPayload for /aspects --aspect event.catalog. Use when extracting the event.catalog aspect. Reads AsyncAPI specs, Kafka/kafkajs configs, AWS SQS/SNS/EventBridge infra-as-code, RabbitMQ, Google P

• grounding

  How /ground decides which board nodes are substantiated by which repo documents — the citation quality bar, drift handling, and per-genre reading priority. Use during /ground's evidence-proposal step, or whenever judging if a document backs a node's claim. Defines what counts as substantiation, anch

• insight-writing

  How to write the words of a ProvenMap insight or context board — the one contract for every flow that authors them. Use whenever you fill an InsightDraft's name, insight, impact, advice or trail notes, a push's info line, or a context board's name, description and node notes (/insights, /discover, a

• insights

  Bundled Node.js CLI scripts for fetching server-defined insight skills and pushing analysis results to the ProvenMap Claude Code Plugin API. Provides pmap-insights.js for skill caching, insight persistence, and server push. Self-contained — no npm install required.

• monitoring-correlation

  How /monitor turns raw monitoring output (Sentry issues, CloudWatch alarms, cost anomalies) into normalized signals, correlates them with board elements, and shapes work-item-ready insights. Use when running /monitor, normalizing vendor monitoring data, or deciding how an operational signal maps ont

• outcome

  How every ProvenMap command closes — the Outcome you write from the script's brief. Use at the last step of any command or routed workflow, when the step says "Done · Left · Next" or names --brief. Covers the fixed shape, the eight writing rules with examples, how to read a brief (state, gates, cand

• pages-aspect-extraction

  Extracts a repository's frontend routes/pages (route tree, render tree, data dependencies, guards, forms) into a UiPagesPayload for /aspects --aspect ui.pages. Use when extracting the ui.pages aspect. Reads Next.js App/Pages Router, Remix, TanStack Router, React Router, SvelteKit, or Nuxt route file

• platform-driven-build

  How to build an app from the ProvenMap platform's spec — reading compiled skills as the primary spec, turning designed board elements into components, materializing aspect snapshots (DB schema, API surface) as migrations and contracts, and closing the loop so the board maps the built app. Carries th

• provenmap-integration

  Integrates with the Claude Code Plugin API to push architecture data for visualization on ProvenMap workboards. Use when user asks to "sync to ProvenMap", "push architecture to portal", "configure API", "connect to portal", "upload nodes", or "sync edges". Provides API patterns, authentication, and

• report-bug

  How to draft a ProvenMap bug report that describes the problem without naming the user's project. Use at /report-bug's drafting step. Covers what to keep (the scenario), what never goes in (the user's names and content), the report template, and how to generalise a failure.

• ui-inspection

  Interpret pmap-inspect sessions — screenshots, picked components, annotations — and turn them into precise code changes or work item language. Use when reading .provenmap/inspections/ manifests, after /inspect completes, or when component identity in a session needs improving. Covers the identity la

• work-item-gap-review

  Review an architect-authored work item against current code reality before implementing it, then classify the gap as clean, minor, or blocking. Used by /work-items Step 4.5 to decide whether to implement, or bounce the work item back to the architect for clarification. Provides the gap-table method,

Slash commands (25)

• /pmap-code:adopt

  Map · Renamed — this command is now /aspects, with the same flags

• /pmap-code:analyze-archetypes

  Customize the archetype vocabulary — scan for gaps in the catalogue and propose the missing archetypes

• /pmap-code:analyze

  Map · Analyze codebase architecture with layered board support

• /pmap-code:aspects

  Map · Extract a code aspect (database schema, API surface, API clients, frontend pages, event catalog, or authz registry) onto the bound board

• /pmap-code:build

  Build · Build the app from the platform's spec — compiled skills, work items, board design, aspect contracts. WRITE-CAPABLE: creates and edits project files (after you approve the plan)

• /pmap-code:changes

  Understand · Read this repo's git history into change periods — who did what, when, which rules fired — one record per week or month, pushed to ProvenMap

• /pmap-code:configure

  Account · Configure ProvenMap credentials and settings

• /pmap-code:decisions

  Build · Compile the accepted architecture decisions (ADRs) that govern this app into skills your agent loads. WRITE-CAPABLE: writes ADR skill files; replaces local edits to them.

• /pmap-code:discover

  Understand · Discover the insights and context boards worth showing — ranked by the graph, read in your code, picked by you or chosen for you, authored in parallel, pushed to ProvenMap

• /pmap-code:ground

  Map · Ground the board in this repo's documents — mirror the authored board (or read the analysed one), link evidence, report drift

• /pmap-code:help

  Account · List all pmap-code commands with descriptions and the plugin version

• /pmap-code:insights

  Understand · Run server-defined insight analysis on your architecture board

• /pmap-code:inspect

  Map · Visually inspect the running app — pick components in a real browser, capture screenshots and metadata that feed work items

• /pmap-code:login

  Account · Sign in to ProvenMap in the browser and pick a board (no copy-paste)

• /pmap-code:logout

  Account · Disconnect this project from ProvenMap (clears local credentials)

• /pmap-code:monitor

  Operate · Correlate monitoring signals (errors, logs, cloud costs, issues) with your architecture board and push findings as insights

• /pmap-code:report-bug

  Account · Draft a bug report with your project details removed, to post in the ProvenMap community or send to support

• /pmap-code:restyle

  Map · Restyle an analyzed board on demand — offline signals, a styling plan you approve, applied to the platform

• /pmap-code:scheduled-runs

  Operate · Folded — /start prints the task to create when nothing runs on a schedule; /status lists the runs

• /pmap-code:skills

  Build · Compile this project's ProvenMap skills into the repo. WRITE-CAPABLE: writes IDE-native skill files (never overwrites your local edits).

• /pmap-code:start

  Start here · Start here — reads this project's real state and tells you exactly what to run next

• /pmap-code:status

  Account · Show ProvenMap sync status and analysis summary

• /pmap-code:sync

  Map · Sync architecture analysis to ProvenMap

• /pmap-code:update

  Account · Update this plugin to the latest published version

• /pmap-code:work-items

  Build · Pull architect-authored work items for your board and implement them here. WRITE-CAPABLE: edits project files, with your approval at each step

Subagents (5)

• architecture-analyzer

  Use this agent when the user asks to "analyze codebase structure", "map architecture", "detect tech stacks", "identify components", "create architecture diagram", or when comprehensive codebase analysis is needed for ProvenMap integration. Supports JavaScript/TypeScript (with Vue and Svelte componen

• change-period-author

  Writes the words of ONE change period in the /changes draft — each thread's headline `title` and `what`, the impact of each rule a thread hit, and what each files-triggered rule's yes means with its headline `title` — from the working material the script computed. Dispatched by /changes when a run h

• comparison-board-author

  Draws ONE comparison's two boards — each side's apps with the contracts that differ inside them, the same boxes in the same places on both, callers wired to the contract they call — from the drawing brief /aspects wrote, into one payload file. Dispatched by /aspects after its pushes, one agent per c

• insight-author

  Authors ONE /discover brief into its pushable payload — an insight push (evidence prose around a script-chosen trail) or a context-board payload (name, question, description and per-node notes around a script-drawn board). Dispatched by /discover, one agent per brief, in waves; never invoked for ope

• relationship-detector

  Use this agent when the user asks to "find dependencies", "detect relationships", "map imports", "identify connections", "analyze data flow", or when building edges between components for architecture visualization. Supports JavaScript/TypeScript (with Vue and Svelte components), Python, Java, Go, C

Hooks (2)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-config.sh"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/pmap-dispatch-log.js"

Similar plugins