Sync Docs to AI Agents Instantly

This bundle sets up a working documentation-sync loop between an Obsidian vault and whichever AI coding tool you use - Claude Code, Cursor, or Windsurf - in about 5 minutes. It ships four pre-configured files: .claude/CLAUDE.md (rules for Claude Code), .cursor/rules/docs-sync.mdc (rules for Cursor), .windsurfrules (rules for Windsurf), and docs/example-mapping.md (a setup guide with tips). You install the EVC Local Sync plugin in Obsidian via BRAT (adding entire-vc/evc-local-sync-plugin as a beta plugin and enabling it), copy the rule config matching your AI tool into your project, and create a mapping in Obsidian between your project's repo path and a folder in your vault, with docs set as the subfolder and the sync direction set to bidirectional.

Once that mapping is created and a first sync runs, your AI agent reads fresh /docs content on every request while you keep editing documentation directly in Obsidian - changes in either location propagate to the other automatically, rather than the docs living in two disconnected places that quietly drift apart as one gets updated and the other doesn't.

Use this bundle when you want your AI coding assistant to work from documentation you actually maintain in Obsidian, rather than stale docs baked into the repo or manually duplicated between your vault and your codebase. It's built for a specific, opinionated stack: Obsidian as the documentation source of truth, one of Claude Code, Cursor, or Windsurf as the AI tool, and the EVC Local Sync plugin as the bridge connecting them.

It is not useful without Obsidian and the EVC Local Sync plugin installed, and its bundled rule configs only cover the three named AI tools - if your AI coding tool is something else entirely, the pre-configured files here won't apply directly.

1. Install BRAT from Obsidian's Community Plugins, then use it to add entire-vc/evc-local-sync-plugin as a beta plugin and enable EVC Local Sync in Community Plugins.
2. Copy the rule config for your AI tool into your project - cp -r .claude/ /path/to/your/project/.claude/ for Claude Code, cp -r .cursor/ /path/to/your/project/.cursor/ for Cursor, or cp .windsurfrules /path/to/your/project/.windsurfrules for Windsurf.
3. In Obsidian, go to Settings > EVC Local Sync > Add Mapping, and set the AI project path (your repo), the Obsidian folder to sync into, docs as the docs subfolder, and Bidirectional as the sync direction.
4. Run your first sync and start editing - your AI agent will read the synced /docs on every request from then on.

Developers using Claude Code, Cursor, or Windsurf who keep project documentation in Obsidian and want it to stay in sync with their codebase automatically, instead of manually copying docs back and forth or letting them drift out of date.