plugins/learning/skills/forcegraph-exporter/SKILL.md
Export a mindmap JSON outline as an interactive HTML file using force-graph (requires internet for CDN). Use this skill when the user wants an interactive, web-based, zoomable/draggable visualization of a mindmap. TRIGGER WHEN: the user says 'interactive map', 'force graph', 'web mindmap', 'HTML mindmap', or asks for a visual/interactive export. DO NOT TRIGGER WHEN: the user wants Obsidian MarkMind format (use markmind-exporter) or a static text outline.
npx skillsauth add acaprino/alfio-claude-plugins forcegraph-exporterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convert a mindmap JSON outline into an interactive HTML file with a force-directed graph visualization powered by force-graph. The output file can be opened in any browser -- no server required, but needs internet to load the force-graph library from CDN.
A JSON file with the standard mindmap outline format (same as generate-mindmap output):
{
"root": "Central Theme",
"branches": [
{
"text": "Branch One",
"color": "#ff6b6b",
"children": [
{ "text": "Sub-concept A", "children": [...] }
]
}
]
}
If no mindmap JSON is available (no file path, no prior generate-mindmap output, no inline JSON in the conversation), invoke the learning:generate-mindmap skill first to brainstorm and produce the JSON outline. Then continue with Step 1.
Find the mindmap outline JSON -- either a file path provided by the user, output from a prior generate-mindmap invocation, or inline JSON.
python scripts/generate_forcegraph.py --input outline.json --output /path/to/mindmap.html --max-depth 6
Or from stdin:
cat outline.json | python scripts/generate_forcegraph.py --output /path/to/mindmap.html
Options:
--max-depth N -- maximum depth levels below root (default: 6, max: 10)The script:
.html filePresent the generated .html file to the user. Mention it can be opened directly in any browser.
development
Quality gates for multi-reviewer code review pipelines: adversarial verification panel, completeness critic, reviewer pipeline conventions, and the context sharing pattern for parallel reviewers. TRIGGER WHEN: running /senior-review:team-review quality gates; running /senior-review:code-review Steps 4b/4c (adversarial verification and completeness check); consolidating or deduplicating findings from multiple parallel reviewers. DO NOT TRIGGER WHEN: single-reviewer style review without a consolidation phase, or generic team coordination (the upstream agent-teams skills cover that).
development
Knowledge base for pure-architecture decisions on when to unify duplicated logic into a shared abstraction versus leave it duplicated. Covers the canonical theory (Rule of Three, DRY/WET/AHA, Wrong Abstraction, Locality of Behaviour, Bounded Contexts, Tidy First options framing, CUPID vs SOLID), 12 essential-duplication patterns that justify unification, 12 wrong-abstraction patterns that justify inlining or decomposition, an operational decision frame, and a verified reading list. TRIGGER WHEN: the user is making an architectural decision about whether to centralize, extract, or remove a layer; reviewing an abstraction for premature generality; auditing scattered cross-cutting concerns; spawned by the abstraction-architect agent during /abstraction-architect:audit or as the Abstraction dimension of /senior-review:team-review or /senior-review:code-review; the user asks "should I extract this into a service" / "is this DRY enough" / "is this wrong abstraction". DO NOT TRIGGER WHEN: the task is code formatting and readability cleanup (use clean-code:clean-code), Python-specific refactoring with metrics (use python-development:python-refactor), generic dead-code removal (use senior-review:cleanup-dead-code), security review (use senior-review:security-auditor), or pure pattern-consistency review without an architecture lens (use senior-review:code-auditor).
development
Unified web frontend knowledge base covering CSS architecture, UX psychology, UI components, distinctive aesthetics, and interface design generation. TRIGGER WHEN: working on web styling, design systems, component decisions, responsive strategy, distinctive frontend aesthetics, or exploring multiple interface designs. DO NOT TRIGGER WHEN: the task is purely backend or unrelated to web frontend.
development
Stripe payments knowledge base - API patterns, checkout optimization, subscription lifecycle, pricing strategies, webhook reliability, Firebase integration, cost analysis, and revenue modeling. Loaded by stripe-integrator and revenue-optimizer agents; also consumable directly when the user asks for Stripe-specific patterns without needing an agent. TRIGGER WHEN: working with Stripe API (Payment Intents, Customers, Subscriptions, Checkout Sessions, Connect, webhooks, tax, usage-based billing), pricing strategy, or revenue modeling. DO NOT TRIGGER WHEN: payment work is non-Stripe (PayPal, Square, crypto) or the task is generic e-commerce unrelated to payments.