archmap

Plugin archmap from marketplace quality-gates in AleksandarBisevac/claude-plugins. Commands read from the repo's manifest — 4 days ago.

Skills (4)

• node

  Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type strippin

• webapp-testing

  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

• archmap-review

  Code review for the archmap plugin repository. Checks a diff against the invariants that matter here and that generic review misses - a public repo that must carry no client material, zero npm dependencies on Node 18, deterministic script output, offline self-contained HTML, a backward-compatible mo

• architecture-map

  Use to map or refresh the architecture of a code repository: which components or services exist, what calls what, what each reads or writes in databases, queues and external APIs, and how requests and background jobs flow. Trigger on requests for C4 or container diagrams, architecture or onboarding

Slash commands (6)

• /archmap:build

  Build the evidence-backed architecture map of this repository - model, layout and a self-contained offline HTML viewer in docs/architecture/.

• /archmap:check

  Check whether the architecture map is behind HEAD. Script only, no analysis and no model run; exit 0 when fresh, 1 when stale.

• /archmap:export

  Export the architecture model as Mermaid, PlantUML, SVG, PNG or Markdown files, with no analysis and no model run. Exports are clean, with no issues.

• /archmap:issues

  Review the architecture map for architecture-level issues, optionally importing open audit findings; the overlay is written outside the repository.

• /archmap:render

  Re-render the architecture map HTML from the existing model, with no analysis and no model run. Default is the clean build in docs/architecture/.

• /archmap:update

  Refresh the architecture map after code changes - re-analyses only the areas git says changed, keeps locked nodes, notes and pinned positions.

Subagents (3)

• archmap-explorer

  Reads one area's prescan summary, confirms it against the code, adds what prescan cannot see, writes one size-capped JSON fragment of nodes, edges, entities and access rows with evidence to the fragment path it is given, and replies with three lines. Use it once per area during /archmap:build and /a

• archmap-reviewer

  Reviews the architecture model for architecture-level issues - security, data, reliability, performance, design and docs - and writes them as an issues list anchored to model ids to the reviewer path its brief names, replying in three lines. Use it only when /archmap:build or /archmap:issues runs wi

• archmap-synthesizer

  Reads the merge digest (node ids, edges, entities, access rows and pre-drafted sequences) and writes the narrative layer - 3-7 sequences and the views - as one JSON object to the synth path its brief names, replying in three lines. Use it after merge in /archmap:build, and only for touched sequences

Hooks (1)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/staleness.mjs"

Similar plugins