agentsclimarketplace

Mappamind

Skill mappamind/mappamind/plugins/mappamind/skills/mappamind

See what your AI coding agent just did to your system's behavior, flow, and architecture. Grounded in real code, visual, in-session at the accept moment.

Install
npx -y skills add mappamind/mappamind --skill mappamind

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use Mappamind to set up the first workspace baseline, snapshot before an AI coding agent session, render the shift card after changes, and include local Studio/card URLs in the final response.

SKILL.md

2.5 KB, as published. Nobody here has run it

Mappamind

Use this skill when a user wants Mappamind enabled for a repo/workspace, asks for the initial architecture map, wants an impact card for an AI coding agent session, asks to inspect what the agent changed, or explicitly invokes Mappamind.

Workflow

  1. Check Mappamind status for the current git repo or parent workspace:
mappamind status "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" --json
  1. If the command is missing, tell the user to install the CLI:
npm i -g mappamind-cli
  1. If status reports baseline.state as missing or stale, ask the user before running the expensive initial map. After approval, run:
mappamind setup "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" --host claude --yes

If setup prints studio: file://..., include that URL in the response under Mappamind Studio.

Baselines are local to the repo/workspace path, not to each git branch. A branch checkout can make the stored baseline stale; shifts still compare the session-start snapshot to the session-end tree.

  1. Before making code edits in a session, run:
mappamind snapshot "$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
  1. After meaningful code changes and before the final response, run:
mappamind shift "$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

  1. If the command prints card: file://..., include that URL in the final response under Mappamind card.

  2. If the command folds the card, report the folded reason instead of inventing an impact.

  3. If browser opening fails, still relay the file:// URL. The Studio is one self-contained app at .mappamind/index.html with four tabs (Studio, Shifts, Capabilities, Contracts) — no server, no scripts. A non-cosmetic shift card is written at .mappamind/shift/latest.html and archived per session at .mappamind/shift/<timestamp>.html; the Shifts tab links to every archived card.

Notes

  • Platform-specific packages can bundle lifecycle hooks; users may need to review or trust those hooks in their agent.
  • If status.hooks.warnings mentions duplicate Codex project hooks, tell the user to run mappamind hooks --remove --agent codex in the target root.
  • Opening can be suppressed with MAPPAMIND_OPEN=0.
  • Mappamind depends on the mappamind CLI being available on PATH.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.