loursCreatifloursCreatif/ours-stack/mind-map/SKILL.md

mind-map

Skill1 starsChanged 4 months agoMITView on GitHub

Carte mentale interactive — extraction hiérarchique depuis brief/notes/report vers mind-map.json éditable + mind-map.html autonome (pan/zoom, expand/collapse, liens sources). Zero CDN. Presets partagés avec layout-html. Pas de recherche. Déclencheurs : "mind map", "carte mentale", "mind-map", "vue hiérarchique". Commande : /mind-map.

1 other project uses a version of this.

Adopted by

Most recently taken up by

Whatscheap/igly-canvas-plugintheir own version, first seen Oct 17, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
Whatscheap/igly-canvas-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bear-hoursSkill
- councilSkill
- deep-researchSkill
- dense-readSkill
- dialogueSkill
- infographicSkill
- layout-htmlSkill
- memory-palaceSkill
- source-scoutSkill
- study-statusSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Default when skipped: warm for all inputs.
line 53
Distinctive:
Guard: no text and no resolvable slug → ask for content or path.
line 76
Very specific:
Use importance only for visual hierarchy: 5 root / central thesis, 4 major branches, 3 supporting concepts, 2 details or examples, 1 …
line 84
Very specific:
Leave top-level layout omitted or "auto" by default.
line 86
Very specific:
Write mind-map.json with accurate meta.nodeCount
line 98

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Mind Map

Carte mentale cliquable — plus rapide à parcourir qu'un article linéaire, moins immersif qu'un palais 3D.

When to use (vs other skills)

Skill	Responsibility	Does NOT
`/layout-html`	Article linéaire + SVG figures	Arbre hiérarchique
`/mind-map`	This skill — carte mentale interactive	Nouvelle recherche
`/deep-research`	Synthèse + sources-index	Carte mentale

Optional pipeline (never auto-chained):

/bear-hours → notes / dense-read → /mind-map
/deep-research → /mind-map

Hard rules

No research — never WebSearch / WebFetch. Work only from provided text/files.
Zero external assets — no CDN, no Google Fonts, no external scripts/images/stylesheets, no fetch().
JSON is source of truth — mind-map.json editable; HTML regenerated from JSON.
Faithful to source — never invent URLs, claims, or nodes absent from input.
Limits — max 80 nodes, depth 5. Overflow → merge siblings into one detail with bullet note (deterministic, no ask).
Escape output — embed JSON via structured serialization only; never inject raw markdown HTML into template.
Open browser — open <path> on macOS after write.

Step 0: Style — AskUserQuestion

Title: Mind Map — Style

Offer exactly these 4 options (AskUserQuestion max): warm, editorial, minimal, creative. Custom style goes through the automatic "Other" option — treat the free text as a custom preset per references/presets.md § Custom. Smart-skip if one of these presets is named in message.

Default when skipped: warm for all inputs.

Load references/presets.md and token blocks from references/html-template.md.

Step 1: Intake — detect input mode

Mode	Trigger	Source	Output
A — Study	`studies/<slug>/` or slug	`brief.md` + optional `notes.md`	`studies/<slug>/mind-map.{json,html}`
B — Research	`research/<slug>/`	`report.md` + optional `sources-index.md`	`research/<slug>/mind-map.{json,html}`
C — File	path to `.md`	that file	`<dir>/mind-map.{json,html}`
D — Pasted	text in chat	message body	`output/mind-map/<slug>/map.{json,html}`
E — Regenerate	`regenerate` / existing JSON	`mind-map.json` only	regen HTML only

Invocation examples:

/mind-map biomimetisme-locomotion-chantier
/mind-map studies/biomimetisme-locomotion-chantier/brief.md
/mind-map research/robots-assemblage-structurel-chantier
/mind-map regenerate studies/foo/mind-map.json

Guard: no text and no resolvable slug → ask for content or path.

Step 2: Extract hierarchy

Load references/extraction-rules.md and references/node-schema.md.

Parse markdown headings, bullets, source lines. Assign id, type, label, summary, note, href, collapsed, and optional importance.

Use importance only for visual hierarchy: 5 root / central thesis, 4 major branches, 3 supporting concepts, 2 details or examples, 1 sources or minor leaves. Omit it when unsure; the HTML renderer infers a safe size.

Leave top-level layout omitted or "auto" by default. Set "centered" only when the source is clearly wide/exploratory and shallow; set "tree" only when the user explicitly wants the classic hierarchy.

Run validation:

python3 mind-map/scripts/validate-map.py "<path>/mind-map.json"

On validation error → fix JSON before composing HTML.

Step 3: Write JSON then HTML

Write mind-map.json with accurate meta.nodeCount
Compose HTML:

python3 mind-map/scripts/compose-html.py "<path>/mind-map.json"

Or hand-compose from references/html-template.md if script unavailable.

Overwrite without asking unless file modified <1h ago and user didn't say overwrite.

Step 4: Deliver

open "<absolute-path>/mind-map.html"

Tell the user:

Output paths (json + html)
Style preset used
Input mode
Node count by type (concept, detail, example, source); mention summary / note coverage when present
Reminder: edit mind-map.json then /mind-map regenerate <path>

Errors (deterministic)

Condition	Action
Empty / unparseable markdown	Stop — ask for clearer structure or paste headings
No brief (study mode)	Suggest `/bear-hours` first
>80 nodes after extraction	Merge deepest siblings into grouped `detail` until ≤80
Duplicate `id`	Regenerate ids with slug prefix
`source` without `href`	Keep node; panel shows label only
Invalid JSON (regenerate)	Stop — show `validate-map.py` error
`compose-html.py` missing	Fall back to template in `references/html-template.md`

Escape hatches

User says	Action
`regenerate`	Mode E — JSON → HTML only
`overwrite`	Replace without confirmation
`warm` / `editorial` / `minimal` / `creative`	Smart-skip style question
Described style ("sombre néon", "pastel"…)	Smart-skip — custom preset per `references/presets.md` § Custom (`meta.customTokens`)
slug only	Try `studies/<slug>/` then `research/<slug>/`

Self-check before delivery

No WebSearch / WebFetch
All nodes traceable to input
≤80 nodes, depth ≤5
validate-map.py passes
HTML offline-ready (no external URLs in assets)
JSON + HTML written + browser opened

References

references/node-schema.md — JSON contract
references/extraction-rules.md — markdown → tree
references/html-template.md — manual compose fallback
references/presets.md — layout-html token alignment
references/design-decisions.md — design decision log
scripts/validate-map.py — schema check
scripts/compose-html.py — JSON → HTML

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free