From mb
Initialize MindBase — set knowledge base directory and create PARA structure
How this command is triggered — by the user, by Claude, or both
Slash command
/mb:setupThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# MindBase Setup ## Your Task Guide the user through setting up their MindBase knowledge base. This should be run after installing the plugin or when the user wants to reconfigure. ## Process ### Step 1: Check Existing Settings Read `~/.claude/plugins/mindbase/config.json` to check if MindBase is already configured. - If it exists, show the current path and ask if the user wants to reconfigure. - If it doesn't exist, proceed to Step 2. ### Step 2: Ask for MindBase Location Ask the user where they want their MindBase directory. Default: `~/Documents/MindBase/` Suggest common options...
Guide the user through setting up their MindBase knowledge base. This should be run after installing the plugin or when the user wants to reconfigure.
Read ~/.claude/plugins/mindbase/config.json to check if MindBase is already configured.
Ask the user where they want their MindBase directory. Default: ~/Documents/MindBase/
Suggest common options:
~/Documents/MindBase/ (default, good for Obsidian)~/MindBase/The path must be an absolute path (after expanding ~).
If the directory doesn't exist, create the full PARA structure:
mkdir -p <path>/{00_Inbox,01_Projects,02_Areas,03_Resources,04_Archive}
Create _index.md in each subdirectory if not present, and create index.md at root if not present.
Also create CLAUDE.md and README.md at root if not present (use the standard templates from the kb-agent AGENT.md definition).
Write the configuration to ~/.claude/plugins/mindbase/config.json (create the mindbase directory if needed):
{
"mindbase_path": "/absolute/path/to/MindBase",
"configured_at": "YYYY-MM-DD"
}
Automatically grant Claude Code read/write permissions for the MindBase directory so users don't need to approve every file operation.
~/.claude/settings.jsonpermissions or permissions.allow doesn't exist, create it as an empty array.<path> with the absolute MindBase path):
Read(<path>/**)Write(<path>/**)Edit(<path>/**)Bash(mkdir -p <path>:*)~/.claude/settings.json, preserving all other settings.Important: Be careful to preserve ALL existing settings in the file (env, model, plugins, etc.). Only modify the permissions.allow array.
Show the user:
MindBase setup complete!
Path: /absolute/path/to/MindBase
Structure: PARA (Inbox / Projects / Areas / Resources / Archive)
Permissions: Read/Write/Edit auto-approved for MindBase directory
You can now use:
/kb:record — Save knowledge from conversations
/kb:search — Search your knowledge base
/kb:sort — Organize and health-check entries
/kb:think — Explore ideas with a thinking partner
~ to the full home directory path before savingnpx claudepluginhub foresx/mindbase-plugin --plugin mb/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.