vibemap

Bulk-migrate legacy VibeMap nodes from scripts/legacy-nodes.js into rich raw/nodes/<id>.md files with 3-language bodies, wiki-links, and canonical refs. Use when the user asks to "보강 / enrich / migrate / flesh out / 승격" one or more existing (legacy) VibeMap nodes. Accepts a list of node ids, or the phrase "top-N by degree" to auto-select highest-connected legacy nodes. Reuses the authoring patterns from vibemap-add-node but starts from an existing legacy body/title instead of a blank keyword.

Add a new concept/service/tool node to VibeMap. Use when the user asks to add a node, concept, service, or tool to VibeMap — e.g. "VibeMap에 AppRunner 추가", "add a node for Kubernetes", "VibeMap에 새 개념 추가해줘", "노드 추가해줘 — X", or after a conversation concludes "이것도 지도에 넣는 게 좋겠다." Researches the keyword via Perplexity/Exa, authors raw/nodes/<id>.md with 3-language body and [[wiki-link]] connections, runs make compile, and stages a commit.