メニュー
Generate mind map images using mind-elixir. Produces PNG or SVG files from plaintext input. Use when the user needs a mind map, concept map, or topic overview diagram.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mindmap |
| description | Generate mind map images using mind-elixir. Produces PNG or SVG files from plaintext input. Use when the user needs a mind map, concept map, or topic overview diagram. |
| allowed-tools | Bash, Write, Read |
| argument-hint | <topic or "plaintext content"> [--dir mindmaps] [--format png|svg] [--theme academic|latte|dark] [--direction side|right|left] [--typst] [--caption "..."] |
Generate a mind map image from a topic or plaintext mind map content.
If {baseDir}/scripts/node_modules does not exist, run:
cd {baseDir}/scripts && npm install
Generate plaintext mind map content from $ARGUMENTS. If the user provides a short topic, expand it into a full mind map tree (3-4 branches, 3-5 leaves each). If the user provides plaintext content, use it directly.
Write the plaintext to a temp file at /tmp/mindmap-input.txt.
Run the script to render the mind map:
node {baseDir}/scripts/generate_mindmap.mjs -i /tmp/mindmap-input.txt -o "<output-path>" [flags...]
open <path>.Use mind-elixir plaintext: a markdown-style indented list. Two-space indentation per level.
- Root Topic
- Branch 1
- Leaf 1a
- Leaf 1b
- Leaf 1c
- Branch 2
- Leaf 2a
- Leaf 2b
- Branch 3
- Leaf 3a
- Leaf 3b
- Leaf 3c
Keep topics short (2-5 words per node). Aim for 3-5 branches, 3-5 leaves per branch, max 3 levels deep.
For node colors, arrows, and summaries, see references/advanced-syntax.md.
-i input, -o output, -f png|svg, -t academic|latte|dark, -d side|right|left, -s scale (default 3), --typst, --caption "...", --typst-width 90%
Defaults: --dir mindmaps/, auto-generates filename from topic.
For /mindmap "Portfolio Theory":
node {baseDir}/scripts/generate_mindmap.mjs \
-i /tmp/mindmap-input.txt \
-o "mindmaps/portfolio-theory.png"
Create new documents in any format — Beamer slides, Typst documents, or Quarto slides. Autonomous pipeline from prompt to publication-quality output.
Syntax guide and ecosystem reference for writing Typst (.typ) files. Use this skill when writing, editing, or debugging Typst documents. Covers core syntax, common errors, packages, and best practices.
Master pipeline — compile, review, fix, and finalize any document. Auto-detects format and runs the full quality loop.
Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.
Compile any supported file type. Detects format (.typ, .qmd, .py) and runs appropriate build command.
Show current context status and session health. Use to check how much context has been used, whether auto-compact is approaching, and what state will be preserved.