Scaffold the PKM system onto an existing Obsidian vault. Scans your vault structure, maps folders interactively, and generates configuration — no template required.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Scaffold the PKM system onto an existing Obsidian vault. Scans your vault structure, maps folders interactively, and generates configuration — no template required.
Replace {mapped-*} with actual folder names from Phase 2.
4b. Write root CLAUDE.md
Generate a root CLAUDE.md that describes the user's actual vault structure. Use the same format as the template's CLAUDE.md but with:
Their folder names in the Directory Structure table
Their goal areas in the System Purpose section
Their actual skills table (same as template)
Cascade section adapted to their folder names
If the user had an existing CLAUDE.md, merge their content into the appropriate sections (preserve their mission statement, custom conventions, etc.).
4c. Write vault-config.json
Write vault-config.json in the vault root:
{"name":"User's name","reviewDay":"Sunday","goalAreas":["Career & Professional","Health & Wellness"],"workStyle":"Direct and concise","setupDate":"2026-02-17","version":"3.1","adoptedVault":true,"folderMapping":{"dailyNotes":"Daily","goals":"Goals","projects":"Projects","templates":"Templates","archives":"Archive","inbox":"Inbox"}}
4d. Set Environment Variables
Write or update CLAUDE.local.md with env var exports for hooks:
## Environment Overrides
These env vars allow hooks and scripts to find your folders:
<!--
Export these in your shell profile or they'll be set by session-init:
-->
DAILY_NOTES_DIR={mapped daily notes folder}
GOALS_DIR={mapped goals folder}
PROJECTS_DIR={mapped projects folder}
TEMPLATES_DIR={mapped templates folder}
INBOX_DIR={mapped inbox folder}
ARCHIVES_DIR={mapped archives folder}
Also create .claude/hooks/adopt-env.sh that exports these variables:
#!/bin/bash# Environment variables for adopted vault folder mapping# Generated by /adopt — edit vault-config.json and re-run /adopt to updateexport DAILY_NOTES_DIR="{mapped daily notes}"export GOALS_DIR="{mapped goals}"export PROJECTS_DIR="{mapped projects}"export TEMPLATES_DIR="{mapped templates}"export INBOX_DIR="{mapped inbox}"export ARCHIVES_DIR="{mapped archives}"
Then add a source line to session-init.sh if not already present:
# Source adopted vault env vars if present
ADOPT_ENV="$VAULT_PATH/.claude/hooks/adopt-env.sh"if [ -f "$ADOPT_ENV" ]; thensource"$ADOPT_ENV"fi
Phase 5: Scaffold Missing Pieces
Check what's missing and offer to create it. Always ask before creating.
5a. Goal Cascade Files
If the goals folder is empty or newly created:
"Your goals folder is empty. Want me to create the goal cascade? (3-year vision, yearly goals, monthly goals, weekly review)"
If yes: copy the standard templates, adapting paths to the user's folder names
If no: skip
5b. Templates
If the templates folder is empty or newly created:
"Want me to add standard templates? (Daily, Weekly Review, Project)"
If yes: copy templates, adapting internal links to the user's folder names
If no: skip
5c. CLAUDE.local.md.template
If CLAUDE.local.md.template doesn't exist:
Copy it from the standard template
Adapt any folder references
5d. Claude Config Directories
Ensure these directories exist (create silently):
.claude/skills/ (for future skill additions)
.claude/rules/
.claude/hooks/
.claude/agents/
Copy standard rules files if .claude/rules/ is empty:
markdown-standards.md
productivity-workflow.md
project-management.md
task-tracking.md
Phase 6: Verify & Next Steps
6a. Validation
Run quick checks:
vault-config.json is valid JSON (read it back)
All mapped folders exist
CLAUDE.md is present and non-empty
.claude/hooks/adopt-env.sh is present and executable
