Plannotator Visual Explainer

Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.

13,329 stars 1,343 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add backnotprop/plannotator

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add backnotprop/plannotator --skill plannotator-visual-explainer
Manual install
git clone --depth 1 https://github.com/backnotprop/plannotator.git /tmp/plannotator
mkdir -p ~/.claude/skills
cp -r /tmp/plannotator/apps/skills/extra/plannotator-visual-explainer ~/.claude/skills/plannotator-visual-explainer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Plannotator Visual Explainer

Three paths depending on content type. Each has its own references and structure.

## Route by content type

**Implementation plan, design doc, or proposal** → Follow the [Plan path](#plan-path). Read `references/design-system.md` and `references/svg-patterns.md`. Prescriptive structure.

**PR explainer, diff review, or code change walkthrough** → Follow the [PR path](#pr-path). Read `references/design-system.md` and `references/pr-components.md`. Prescriptive structure.

**Everything else** (architecture diagrams, data tables, slide decks, project recaps, general visual explanations) → Follow the [Visual explainer path](#visual-explainer-path). Delegates to nicobailon/visual-explainer with Plannotator theme tokens.

## Delivery

Always deliver via Plannotator's annotation UI. Do NOT use `open` or `xdg-open`.

For any deliverable that uses Mermaid, render every diagram with Mermaid 12 in both the light
and dark palettes before opening the annotation UI. Rendering is a hard gate: an exception,
empty SVG, or error output such as `aria-roledescription="error"` or `Syntax error in text`
means the explainer is not deliverable. Fix the diagram or theme configuration and rerun both
palettes until every SVG passes.

For zoomable diagram shells, additionally zoom to the maximum and pan to all extremes in both palettes before delivering: the figure caption must stay fully legible throughout (see `references/diagram-shell.md`).
Read the full skill on GitHub

Details

Skill name
plannotator-visual-explainer
Path
apps/skills/extra/plannotator-visual-explainer/SKILL.md
License
Apache-2.0
Repo updated
18 November 2026

FAQ

What does the Plannotator Visual Explainer skill do?

Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.

How do I install the Plannotator Visual Explainer skill?

Claude Code plugin: /plugin marketplace add backnotprop/plannotator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Plannotator Visual Explainer popular?

It lives in backnotprop/plannotator, which has 13,329 GitHub stars and 1,343 forks, and is included in 2 curated skill lists.

Related skills

Plannotator

13k

backnotprop/plannotator

Reference for using Plannotator (its `plannotator` tool when you have one, otherwise the CLI): plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, exporting or sharing Guided Reviews, and the Plannotator Inbox (messages and questions the person answers later, without blocking you). Invoke when asked to use Plannotator for anything not covered by a more specific plannotator-* skill, and before you leave the person a decision, a question or finished work in the Plannotator Inbox (if another ag

Software DevelopmentIn 2 lists1.3k

Plannotator Annotate

13k

backnotprop/plannotator

Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.

Frontend & DesignIn 2 lists1.3k

Plannotator Annotate

13k

backnotprop/plannotator

Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.

Frontend & DesignIn 2 lists1.3k

Review Renovate

13k

backnotprop/plannotator

Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations. Use when a Renovate PR updates GitHub Actions in .github/workflows/.

Git & Code ReviewIn 2 lists1.3k

Plannotator Review

13k

backnotprop/plannotator

Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.

Git & Code ReviewIn 2 lists1.3k

Afk

12k

jakubkrehel/skills

Works through a project while you're away, finding improvements and new ideas, building the best of them on a local branch and leaving a report for when you're back.

Git & Code Review483

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.