AI-папка /docs и спеки в Obsidian
в синхронизации

## Documentation Sync Rules

This project uses EVC Local Sync to keep `/docs` in sync with an Obsidian vault.

### When working with /docs:
- Always read the current state of files in `/docs` before modifying
- After changes to specs or documentation, update the corresponding file in `/docs`
- Use clear commit messages referencing which doc was updated
- Do NOT delete files from `/docs` without explicit confirmation

### File structure:
- `/docs/PRD.md` — Product Requirements (source of truth in Obsidian)
- `/docs/architecture.md` — Technical architecture decisions
- `/docs/changelog.md` — Auto-updated changelog

### Sync behavior:
- Changes in `/docs` are automatically synced to Obsidian vault
- Changes in Obsidian are automatically synced to `/docs`
- Conflicts are resolved by keeping both copies (manual merge needed)

---
description: Rules for working with /docs synced via EVC Local Sync
globs: docs/**/*.md
---

# Documentation Sync Rules

The `/docs` folder is bidirectionally synced with an Obsidian vault via Local Sync.

## Rules:
- Read `/docs` files before making changes to understand current state
- Update `/docs` when modifying project specs or architecture
- Never delete `/docs` files without explicit user confirmation
- Reference `/docs/PRD.md` as the source of truth for requirements

## /docs Sync Rules
This project syncs /docs with Obsidian via EVC Local Sync.
- Read /docs before modifying specs
- Keep /docs updated when changing architecture or requirements
- /docs/PRD.md is the source of truth
- Never delete /docs files without confirmation