kenjaku: Skill for Claude Code

/switch — Change or create the active universe (opt-in, no reindex)

Brain-side skill. A universe (ADR 0034) is a soft, engine-enforced retrieval scope over the one shared vault: while a universe is active, search_vault returns that universe's notes plus your cross-cutting (default) notes, and nothing from the others, unless you explicitly ask for "all universes". It is a relevance feature, never an isolation wall (a bug, Obsidian, git or grep can cross it, and for a private brain that is fine).

⚠️ This is a thin conversational driver. All the real, testable logic lives in the deterministic core scripts/set-active-universe.mjs + scripts/lib/universes.mjs (ADR 0009). This skill only reads the current state, runs that core, and reports — it holds no logic and makes no scope decision of its own (the engine reads the active pointer itself, per search).

When to use it

Load this whenever the user wants to change context or manage universes, in plain language, any language:

• "switch to the acme universe" · "passe sur l'univers acme" · "change de contexte"
• "create a universe Blue Team" · "crée un univers Blue Team" · "add a new context"
• "which universe am I in?" · "dans quel univers je suis ?" · "liste mes univers"

🧭 Progressive disclosure. Below two universes there is nothing to manage: a brain with a single (default) universe behaves exactly as today. Do not volunteer universes to a single-universe user. But if they explicitly ask to create one, this skill is the way in.

Golden rules

• No writes to notes, no reindex. Switching only re-points the active-universe pointer under <brain>/.vault-rag/. The engine reads it live on the next search. Never offer a reindex here. (The two lifecycle operations below are the exceptions, and they reindex themselves: renaming a universe moves every one of its notes, deleting one removes them. Still nothing to offer.)
• The core is the single surface. Natural language ("create a universe X") and /switch X route to the same script, so there is never a diverging path (ADR 0009).
• 🔤 Two worlds, two vocabularies — and you never decide which. Below the disclosure gate (a single universe, nothing ever created) the notion does not exist for this user: never write or say universe to them, speak of their context, their world, this place. The moment a second universe exists, the opposite holds: everything is framed as universes, because that is the word they now switch with. The deterministic core tells you which world you are in — ask it, in one command, and it answers BELOW the disclosure gate or PAST the disclosure gate:

  node scripts/set-active-universe.mjs gate
  

  Do not infer it by counting universes yourself (ADR 0009). File paths the core prints (vault/universe.md) are the one exception: a filename is a filename, and quoting it back is fine.
• Creating a universe is create-and-switch (git switch -c ergonomics): register the name and make it active in one move. The name is normalized to a safe kebab slug (e.g. "Blue Team" → blue-team); the reserved name default cannot be created.