Project Linking

Obsidian Project Linking

Overview

CLAUDE.local.md integration for Obsidian vaults. Automatically detects project configuration at session start, loads vault documentation index silently, and enables intelligent routing between vault (exploratory docs) and local repository (implementation docs).

Requires: The vault skill for basic Obsidian vault operations (CRUD, inbox, promotion, validation).

Project Linking Configuration

CLAUDE.local.md detection: Check for CLAUDE.local.md in working directory at session start.

Parse configuration fields:

• Vault project: \project-name`` - Links working directory to vault project
• Local docs: ./path - Optional local documentation directory
• Documentation style: standard - Optional style override

Configuration precedence:

• CLAUDE.local.md overrides for project-specific settings
• ~/.claude/CLAUDE.md for vault path (Primary vault:)
• Defaults: vault path ~/Obsidian/vault, no local docs

Example CLAUDE.local.md:

# Obsidian Project
Vault project: `my-project-name`
Local docs: `./docs`
Documentation style: standard

Session context: Store parsed values in memory for the session:

• project_name - from Vault project field
• local_docs_path - from Local docs field (optional)
• doc_style - from Documentation style field (optional, default: adapt)

Startup Behavior

When CLAUDE.local.md contains Vault project: reference:

1. Silent Index Loading

Trigger: Session starts in directory with CLAUDE.local.md containing Vault project field

Process:

1. Parse CLAUDE.local.md for Vault project: \name``
2. Determine vault path from "Primary vault:" in context
3. Expand ~ to home directory in vault path
4. Construct project path: <vault-path>/projects/<project-name>/
5. Read all .md files in project folder
6. Extract from each file's frontmatter:
   • filename (for reference)
   • type: field (brainstorm, design, plan, notes, retrospective)
   • status: field (planning, active, paused, completed, archived)
7. Store index in memory as session context

Silent Success:

• No output to user
• Index available for search/list operations

Visible Warnings:

• Vault path doesn't exist: "Warning: Vault path <path> not found. Check Primary vault in ~/.claude/CLAUDE.md"
• Project doesn't exist: "Note: Vault project <name> not found - will create on first save"
• Permission error: "Error: Cannot read vault project <name> at <path> - permission denied"

2. Local Docs Verification

If Local docs: configured:

1. Verify directory exists relative to working directory
2. If not found: "Warning: Local docs directory <path> not found. Create it or update CLAUDE.local.md"
3. Do not auto-create (respect project structure)

Session Ready: After startup, Claude knows:

• All vault documents (from index)
• Local docs location (if configured)
• Ready for document operations

Location Resolution

Determine target location for document operations:

Resolution Algorithm

When creating document:
  If user explicitly specifies location:
    Use specified location
  Else if Local docs configured:
    If document type in [design, plan]:
      → Local docs directory
    Else:
      → Vault project
  Else:
    → Vault project (default)

Document Type Categories

Implementation docs (go to local when Local docs configured):

• design - Architecture and technical design
• plan - Implementation tasks and roadmaps

Exploratory docs (always go to vault):

• brainstorm - Initial idea exploration
• notes - Working notes and observations
• retrospective - Post-completion reflections

Location Override Examples

Explicit overrides (user specifies location):

• "save this design to the vault" → vault even if local docs enabled
• "create a plan in docs/" → local even without local docs config
• "save to inbox" → always vault _inbox

Natural routing (no location specified):

• "create a design doc" + Local docs configured → local docs/
• "create a design doc" + no Local docs → vault
• "save this brainstorm" + Local docs configured → vault (exploratory)
• "save this brainstorm" + no Local docs → vault

Location-Specific Conventions

Vault documents:

• Filename: YYYY-MM-DD-descriptive-name.md (lowercase, hyphens)
• Frontmatter: Required (project, status, type, created)
• Linking: Wikilinks [[filename]]
• Updates: Add updated: YYYY-MM-DD to frontmatter

Local documents:

• Filename: Flexible (adapt to existing or use simple names like architecture.md)
• Frontmatter: Optional (not required)
• Linking: Relative markdown links [text](./file.md)
• Updates: Rely on git history (no frontmatter dates)

Local Document Operations

When Local docs: configured, enable operations in local directory:

Style Adaptation

Detect existing project style (default behavior):

1. Read 1-3 existing documents from local docs directory
2. Analyze:
   • Filename patterns (kebab-case, snake_case, PascalCase, date-prefixed, etc.)
   • Heading structure (ATX vs Setext, title format)
   • Frontmatter presence and format
   • Overall tone and structure
3. Match detected style in new documents

Override with standard template:

• If Documentation style: standard in CLAUDE.local.md
• Use consistent template regardless of existing docs

Fallback to standard:

• If local docs empty or unreadable
• Warn: "Couldn't detect local style, using standard template"

GitHub Remote Detection

Purpose: Create portable links from vault docs to local docs

Detection process:

1. Parse .git/config in working directory
2. Look for [remote "..."] sections with url containing github.com
3. Extract: org/repo from URL patterns:
   • https://github.com/org/repo.git
   • git@github.com:org/repo.git
4. Determine default branch:
   • Check .git/refs/remotes/origin/HEAD
   • Common: main or master

Link construction: https://github.com/<org>/<repo>/blob/<branch>/docs/<filename>.md

When to skip linking:

• Non-GitHub remote (GitLab, Bitbucket, self-hosted)
• No remote configured
• Cannot parse remote URL

Multiple remotes:

• Prefer origin if present
• Otherwise use first GitHub remote found

Creating Local Documents

Process for local doc creation:

Step 1: Determine filename

• Adapt to existing style if detected
• Examples: architecture.md, api-design.md, database-schema.md

Step 2: Detect related vault docs

• Search vault index for related documents
• Match by project name, keywords, document type

Step 3: Create document

• Apply adapted style or standard template
• Add optional frontmatter if existing docs use it
• Include content based on user's request

Step 4: Add Related Documents section

• Link to related local docs: [Architecture](./architecture.md)
• Link to related vault docs via GitHub URL (if detected):

  ## Related Documents
  
  - [API Design](./api-design.md) - REST API specification
  - [Initial Brainstorm](https://github.com/org/repo/blob/main/docs/brainstorm.md) - Early ideas
  

Step 5: Confirm creation

• "Created docs/design.md matching project style"
• List any links added

Updating Local Documents

Process:

1. Locate document in local docs directory
2. Read current contents
3. Apply requested changes
4. Do not modify filename (preserve name)
5. Do not add frontmatter dates (rely on git)
6. Confirm changes: "Updated docs/architecture.md"

Searching Local Documents

Combine with vault search:

• "show me design docs" → search vault index + scan local docs
• Report both locations: "Found in vault: ..., Found in docs/: ..."
• Let user disambiguate if multiple matches

List all docs:

• Combine vault index with local directory scan
• Show location for each: [vault] or [local]

Enhanced Operations

These operations extend the vault skill with dual-location awareness:

Create New Project (Enhanced)

Check for project linking:

• If CLAUDE.local.md exists with Vault project: → use that project name as suggestion
• Otherwise → ask for project name

Apply location resolution:

• If Local docs configured AND type in [design, plan] → create in local docs
• Otherwise → create in vault projects//

Generate filename:

• Vault: YYYY-MM-DD-<type>.md
• Local: adapt to style or use <type>.md

Add Document to Project (Enhanced)

1. Check for CLAUDE.local.md with matching project name
2. Apply location resolution:
   • If Local docs configured AND type in [design, plan] → create in local docs
   • Otherwise → create in vault project folder
3. Search both vault and local for related docs
4. Add inline wikilinks (vault) or markdown links (local)
5. Add ## Related Documents section with links:
   • Vault docs: [[YYYY-MM-DD-filename]]
   • Local docs: [Title](./filename.md)
   • Cross-location: GitHub URL if detected

List Projects (Enhanced)

• If CLAUDE.local.md configured, include linked project prominently
• Show vault doc count
• If Local docs configured, show local doc count too

Output:

Active Projects:
- obsidian-integration (3 vault docs, 2 local docs) [*linked]

Planning:
- another-project (1 vault doc)

[*linked] = configured in CLAUDE.local.md

Show Project Contents (Enhanced)

1. Find project folder in vault
2. If CLAUDE.local.md links this project, also scan local docs
3. List vault documents with types/statuses from frontmatter
4. List local documents
5. Present by location, chronologically within each

Output:

obsidian-integration (status: active):

Vault documents:
- 2025-11-07-initial-brainstorm.md (brainstorm)
- 2025-11-10-retrospective.md (retrospective)

Local documents:
- architecture.md (design)
- implementation-plan.md (plan)

Error Handling

Configuration Errors

CLAUDE.local.md missing vault project:

• If CLAUDE.local.md exists but no Vault project: field
• Behavior: Treat as no project linking configured
• No warning needed

Invalid project name format:

• Project name contains spaces or uppercase
• Suggest: "Project name should be lowercase with hyphens: my-project-name"

Both CLAUDE.md and CLAUDE.local.md specify project:

• CLAUDE.local.md takes precedence (project-specific override)
• No warning needed

Startup Errors

Vault path doesn't exist:

• Show: "Warning: Vault path <path> not found. Check 'Primary vault:' in ~/.claude/CLAUDE.md"
• Continue session (non-blocking)

Vault project doesn't exist:

• Show: "Note: Vault project <name> not found - will create on first save"
• Continue session (non-blocking)
• Create on first document save

Permission denied reading vault:

• Show: "Error: Cannot read vault project <name> at <path> - permission denied"
• Continue session but document operations will fail
• Suggest: Check file permissions

Local docs directory missing:

• If Local docs: ./docs configured but doesn't exist
• Show: "Warning: Local docs directory ./docs not found. Create it or update CLAUDE.local.md"
• Continue session (vault still works)

Operation Errors

Ambiguous document reference:

• "show me the design doc" matches both vault and local
• Show both with locations: "Found 2 matches: [vault] 2025-11-15-design.md, [local] architecture.md"
• Ask: "Which document? Specify 'vault design' or 'local design'"

Cannot write to location:

• Vault write fails: "Error: Cannot write to vault at <path> - permission denied. Try local docs instead?"
• Local write fails: "Error: Cannot write to <path> - permission denied. Try vault instead?"

GitHub remote detection fails:

• Non-GitHub remote: No cross-linking, no warning
• No remote: No cross-linking, no warning
• Multiple GitHub remotes: Use origin or first found

Style adaptation fails:

• Local docs empty: "Note: No existing docs found in ./docs, using standard template"
• Cannot read local docs: "Warning: Cannot read local docs for style detection, using standard template"

Common Mistakes

Workflow Examples

Example 1: Vault-Only Configuration

Setup CLAUDE.local.md:

# Obsidian Project
Vault project: `obsidian-integration`

Session Start:

• Claude silently loads index from vault project
• No output unless warnings

User: "Create a design doc" Claude: Creates ~/Obsidian/vault/projects/obsidian-integration/2025-11-15-design.md with frontmatter

User: "Save this brainstorm" Claude: Creates ~/Obsidian/vault/projects/obsidian-integration/2025-11-15-brainstorm.md

Result: All docs in vault, full frontmatter tracking

Example 2: Dual Location Configuration

Setup CLAUDE.local.md:

# Obsidian Project
Vault project: `api-refactoring`
Local docs: `./docs`

Session Start:

• Claude silently loads vault index
• Verifies ./docs exists
• No output unless warnings

User: "Create a design doc" Claude:

1. Detects type: design (implementation doc)
2. Resolves to: local docs
3. Reads existing docs in ./docs to detect style
4. Creates ./docs/architecture.md matching detected style

User: "Save this brainstorm" Claude:

1. Detects type: brainstorm (exploratory doc)
2. Resolves to: vault
3. Creates ~/Obsidian/vault/projects/api-refactoring/2025-11-15-brainstorm.md

User: "List all project docs" Claude:

api-refactoring (status: active):

Vault documents:
- 2025-11-07-initial-brainstorm.md (brainstorm)
- 2025-11-10-retrospective.md (retrospective)

Local documents:
- architecture.md (design)
- api-design.md (design)

Result: Implementation docs version-controlled with code, exploratory docs in vault

Example 3: Cross-Location Linking

Setup:

• CLAUDE.local.md: Vault project: my-app, Local docs: ./docs
• Git remote: github.com/org/my-app

User: "Create a design doc that references the initial brainstorm" Claude:

1. Creates ./docs/architecture.md (local, implementation doc)
2. Searches vault for related docs
3. Finds 2025-11-07-initial-brainstorm.md in vault
4. Detects GitHub remote
5. Adds to design doc:

## Related Documents

- [Initial Brainstorm](https://github.com/org/my-app/blob/main/docs/2025-11-07-initial-brainstorm.md) - Early exploration

Result: Portable bidirectional links that work across machines

Example 4: Style Adaptation

Setup:

• CLAUDE.local.md: Vault project: legacy-app, Local docs: ./documentation
• Existing docs use PascalCase: ApiDesign.md, DatabaseSchema.md

User: "Create a design doc for the authentication system" Claude:

1. Reads existing docs to detect style
2. Detects: PascalCase filenames, specific heading structure
3. Creates ./documentation/AuthenticationDesign.md matching detected pattern

User: Later decides to standardize: adds Documentation style: standard to CLAUDE.local.md

User: "Create a deployment plan" Claude:

1. Checks Documentation style setting
2. Ignores existing PascalCase pattern
3. Creates ./documentation/deployment-plan.md using standard kebab-case

Result: Can adapt to existing conventions or enforce standards

Quick Reference

Benefits:

• Automatic awareness of vault documentation at session start
• Smart routing between vault and local docs based on document type
• Unified view of all project documentation regardless of location
• Portable GitHub links between vault and local docs

Converted and distributed by TomeVault — claim your Tome and manage your conversions.