claudesidian: Skill for Claude Code

Initialize Bootstrap Configuration

This command helps you create a personalized CLAUDE.md configuration file by asking questions about your Obsidian workflow and preferences.

Task

Read the CLAUDE-BOOTSTRAP.md template and interactively gather information about the user's:

• Existing vault structure (if any)
• Workflow preferences
• Note-taking style
• Organization methods
• Specific requirements

Then generate a customized CLAUDE.md file tailored to their needs.

Process

1. Initial Environment Setup

   • Get current date with date command for timestamps
   • Check current folder name and ask if they want to rename it
   • If yes, guide them through renaming (handle parent directory move)
   • Check for package.json and install dependencies:
     • Try pnpm install first (faster, better)
     • Fall back to npm install if pnpm not available
   • Verify core dependencies are installed
   • Check git status:
     • If no .git folder: Initialize git repository
     • If has remote origin: Ask about development work
       • Personal vault: Remove origin and .github folder
       • Contributing: Keep origin and workflows intact
     • If clean local repo: Ready to go
   • Don't create folders yet - wait until after asking about organization method

2. Check Existing Configuration

   • Look for existing CLAUDE.md
   • If exists, ask if they want to update or start fresh
   • Check for CLAUDE-BOOTSTRAP.md template

3. Gather Vault Information

   • Search common locations for existing Obsidian vaults (.obsidian folder)
   • Check these paths with appropriate depth limits:
     • ~/Documents (maxdepth 3) - all platforms
     • ~/Desktop (maxdepth 3) - all platforms
     • ~/Library/Mobile Documents/iCloud~md~obsidian/Documents (maxdepth 5 - macOS only, iCloud vaults)
     • Home directory ~/ (maxdepth 2) - all platforms
     • Current directory parent (maxdepth 2) - all platforms
   • If found, ask: "Found Obsidian vault at [path]. Is this the vault you want to import?"
   • Count files correctly: find [path] -type f -name "*.md" | wc -l (no depth limit)
   • Show vault size: du -sh [path]
   • If confirmed, analyze vault structure:
     • Run tree -L 3 -d [path] to see folder hierarchy
     • Sample 10-15 random notes to understand content types
     • List 30-50 recent file names to detect naming patterns
     • Check for daily notes folder and format
     • Identify most active folders by file count
     • Detect if using PARA, Zettelkasten, Johnny Decimal, or custom
   • If not the right one or none found:
     • On macOS only: Ask: "Is your vault stored in iCloud Drive? (yes/no)"
     • If yes (macOS): "Please enter the full path to your vault (e.g., /Library/Mobile Documents/iCloudmd~obsidian/Documents/YourVault)"
     • If no, or on Linux/Windows: "Please enter the path to your existing vault, or type 'skip' to start fresh"
     • Validate user-provided paths (see "User Path Validation" section below)
   • If no existing vault or user skips, they're starting fresh