chore: sync vault to ~/cosmic-brain (Obsidian-registered path)

commands/autoresearch.md

@@ -0,0 +1,17 @@
+---
+description: Run an autonomous research loop on a topic. Searches the web, synthesizes findings, and files everything into the wiki as structured pages.
+---
+
+Read the `autoresearch` skill. Then run the research loop.
+
+Usage:
+- `/autoresearch [topic]` — research a specific topic
+- `/autoresearch` — ask "What topic should I research?"
+
+Before starting, read `skills/autoresearch/references/program.md` to load the research constraints and objectives.
+
+If no vault is set up yet, say: "No wiki vault found. Run /wiki first to set one up."
+
+After research is complete, update wiki/index.md, wiki/log.md, and wiki/hot.md.
+
+Report how many pages were created and what the key findings are.

commands/save.md

@@ -0,0 +1,16 @@
+---
+description: Save the current conversation or a specific insight into the wiki vault as a structured note.
+---
+
+Read the `save` skill. Then run the save workflow for this conversation.
+
+Usage:
+- `/save` — analyze the full conversation and save the most valuable content
+- `/save [name]` — save with a specific note title (skip the naming question)
+- `/save session` — save a complete session summary
+- `/save concept [name]` — explicitly save as a concept page
+- `/save decision [name]` — explicitly save as a decision record
+
+If no vault is set up yet, say: "No wiki vault found. Run /wiki first to set one up."
+
+Check if a page with the same name already exists. If it does, offer to update it instead of creating a duplicate.

commands/wiki.md

@@ -0,0 +1,23 @@
+---
+description: Bootstrap or check the cosmic-brain wiki vault. Reads the wiki skill and runs setup workflow.
+---
+
+Read the `wiki` skill. Then run the setup workflow:
+
+1. Check if Obsidian is installed. If not, offer to install it (see `skills/wiki/references/plugins.md`).
+2. Check if this directory has a vault (look for `.obsidian/` folder). If yes, report current vault state.
+3. Check if the MCP server is configured (`claude mcp list`). If not, ask if the user wants to set it up.
+4. Ask ONE question: "What is this vault for?"
+
+Then build the entire wiki structure based on the answer. Don't ask more questions. Scaffold it, show what was created, and ask: "Want to adjust anything before we start?"
+
+Examples of what the user might say:
+- "Map the architecture of github.com/org/repo"
+- "Build a sitemap and content analysis for example.com"
+- "Track my SaaS business — product, customers, metrics, roadmap"
+- "Research project on [topic] — papers, concepts, open questions"
+- "Personal second brain — health, goals, learning, projects"
+- "Organize my YouTube channel — transcripts, topics, tools mentioned"
+- "Executive assistant brain — meetings, tasks, business context"
+
+If the vault is already set up, skip to checking what has been ingested recently and offering to continue where things left off.