From accelerator
Launches local web visualizer server for accelerator meta directories (plans, research, decisions, PRs, validations, reviews, notes). Returns URL; supports stop/status subcommands.
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorThis skill is limited to using the following tools:
!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh`
bin/checksums.jsoncli/accelerator-visualiserfrontend/e2e/fixtures.tsfrontend/e2e/global-setup.tsfrontend/e2e/global-teardown.tsfrontend/e2e/kanban-conflict.spec.tsfrontend/e2e/kanban.spec.tsfrontend/e2e/mermaid.spec.tsfrontend/e2e/navigation.spec.tsfrontend/e2e/smoke.spec.tsfrontend/e2e/start-server.mjsfrontend/e2e/wiki-links.spec.tsfrontend/index.htmlfrontend/package-lock.jsonfrontend/package.jsonfrontend/playwright.config.tsfrontend/src/api/fetch.test.tsfrontend/src/api/fetch.tsfrontend/src/api/format.test.tsfrontend/src/api/format.tsLaunches interactive web dashboard via Vite to visualize codebase knowledge graph from .understand-anything/knowledge-graph.json. Requires prior /understand analysis; auto-opens browser.
Opens local web dashboard to browse workflow runs, inspect step timelines, view artifacts, and diff executions side-by-side.
Opens local web UI to view PDCA pipeline results as interactive artifacts: markdown, Nivo charts, Shiki code, SVG flows from session directories via bash scripts.
Share bugs, ideas, or general feedback.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh visualise
Plans directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh plans meta/plans
Research directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh research meta/research
Decisions directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh decisions meta/decisions
PRs directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh prs meta/prs
Validations directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh validations meta/validations
Review plans directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh review_plans meta/reviews/plans
Review PRs directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh review_prs meta/reviews/prs
Templates directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh templates meta/templates
Work directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh work meta/work
Work reviews directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh review_work meta/reviews/work
Notes directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh notes meta/notes
Tmp directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh tmp meta/tmp
Visualiser: !${CLAUDE_PLUGIN_ROOT}/skills/visualisation/visualise/scripts/visualiser.sh "$ARGUMENTS"
The user's argument selects the action. Interpret the
**Visualiser**: line above according to which subcommand was
invoked:
No argument (start) — the line is either:
**Visualiser URL**: <url> — server is running, relay the URL
to the user. Tell them:
/accelerator:visualise returns the same URL
while the server is alive./accelerator:visualise stop.{"error":...} object — the server isn't running.
Read the hint field and relay the remediation.stop — the line is a JSON object describing the result:
{"status":"stopped"} (optionally "forced":true) — the
server has been terminated.{"status":"not_running"} — there was no server to stop.{"status":"refused",...} or {"status":"failed",...} —
relay the reason/error to the user.status — the line is a JSON object: {"status":"running"|"stale"|"not_running","url":...,"pid":...}.
Relay the status (and URL/PID when present) to the user.
{"error":"unknown subcommand",...} — the user passed an
unrecognised argument. Tell them the valid subcommands are
stop and status (no argument starts the server).
By default the plugin downloads a verified per-arch binary from GitHub Releases on first use. Two overrides exist for dev, air-gapped, or pinned-binary workflows:
Environment variable (one-shot, shell-scoped):
ACCELERATOR_VISUALISER_BIN=<path>. Bypasses SHA-256
verification; use for local dev builds.
Config key (persistent, per-project):
---
visualiser:
binary: <absolute or project-relative path>
---
in .claude/accelerator.md (team-committed) or
.claude/accelerator.local.md (personal, gitignored).
Relative paths resolve against the project root.
The team-committed form is trusted on par with the rest of the repo — anyone approving a PR that changes it should treat the value as code, not data.
The release-binary mirror URL can be overridden via
ACCELERATOR_VISUALISER_RELEASES_URL=<base-url> (air-gapped
or proxy-hosted mirrors).
To run the visualiser from a terminal, symlink the CLI wrapper:
Install command: !printf 'ln -s "%s" "%s"' "${CLAUDE_PLUGIN_ROOT}/skills/visualisation/visualise/cli/accelerator-visualiser" "$HOME/.local/bin/accelerator-visualiser"
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh visualise