obsidian-claude-integration

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: obsidian-claude-integration
description: >-
  Comprehensive guide for integrating Obsidian vaults as AI-powered second brains with Claude Code.
  Covers MCP integration, vault manifests, self-evolving patterns, auto-linking, and knowledge
  graph automation. Use when setting up Claude Code + Obsidian workflows, implementing
  bidirectional sync, creating CLAUDE.md manifests, or building self-healing knowledge systems.
---

# Obsidian Second Brain + Claude Code Integration

## Overview

Transform your Obsidian vault into an AI-powered second brain by integrating it with Claude Code.
This skill covers multiple integration patterns from minimal setup to advanced self-evolving systems.

**Key Insight**: An Obsidian vault is essentially a codebase of markdown files. Claude Code is
already excellent at navigating file structures and making surgical edits - no special plugin required.

## Integration Patterns

### Decision Tree

```text
What integration level do you need?
├── Minimal (just works)?
│   └── Pattern A: Direct Access
│       └── Claude Code reads vault directly (no setup needed)
├── Enhanced discovery?
│   └── Pattern B: Manifest-Based
│       └── Add CLAUDE.md to vault root
├── Real-time bidirectional?
│   └── Pattern C: MCP Plugin
│       └── Install obsidian-claude-code-mcp
├── Self-evolving PKM?
│   └── Pattern D: COG Pattern
│       └── Git + automation + self-healing refs
└── Pre-configured structure?
    └── Pattern E: Claudesidian
        └── Adopt opinionated vault structure
```

## Pattern A: Direct Access (Zero Setup)

Claude Code can already read and edit your vault. No configuration needed.

### How It Works

```bash
# Claude Code navigates your vault like any codebase
cd /path/to/your/vault
claude

# Example interactions:
# "Read my daily note from today"
# "Find all notes mentioning project X"
# "Add backlinks to people mentioned in this note"
```

### Best Practices

- Open Claude Code from vault root directory
- Use natural language to describe what you want
- Reference files by name or topic, not exact paths

### Use Cases

| Task | Claude Code Capability |
|------|------------------------|
| Read notes | Direct file access |
| Edit notes | Surgical markdown edits |
| Add backlinks | Find references, insert wikilinks |
| Create notes | Write new files with proper frontmatter |
| Search content | Grep across all markdown files |
| Refactor structure | Move files, update references |

## Pattern B: Manifest-Based (CLAUDE.md)

Add a project manifest to help Claude Code understand your vault's structure and conventions.

### CLAUDE.md Template

Create `CLAUDE.md` at your vault root:

```markdown
# Obsidian Vault Manifest

## Vault Overview
This is a personal knowledge management vault using [describe your system].

## Folder Structure
- `00 - Inbox/` - Quick capture, unsorted notes
- `01 - Projects/` - Active project notes
- `02 - Areas/` - Ongoing responsibilities
- `03 - Resources/` - Reference materials
- `04 - Archive/` - Completed/inactive content
- `Daily/` - Daily notes (YYYY/MM/DD.md format)
- `Templates/` - Note templates

## Conventions
- Frontmatter: Always include `created`, `updated`, `tags`
- Links: Use `[[wikilinks]]` not markdown links
- Tags: Hierarchical (e.g., `#project/client-name`)
- Dates: ISO 8601 format (YYYY-MM-DD)

## Important Files
- `_index.md` - Main dashboard/MOC
- `project-context.md` - Current project context

## When Creating Notes
1. Always add proper frontmatter
2. Include backlinks to related notes
3. Tag appropriately for discoverability
4. Place in correct folder based on type

## When Editing Notes
1. Update the `updated` timestamp
2. Maintain existing link structure
3. Preserve block references (^block-id)
```

See: [templates/CLAUDE.md](templates/CLAUDE.md) for full template.

## Pattern C: MCP Plugin Integration

Real-time bidirectional communication via Model Context Protocol.

### Installation

```bash
# Install the MCP plugin from Obsidian Community Pl