my-vault/.claude/project-instructions.md

# Obsidian PKM Assistant

> Core principles only. See `06_Metadata/WORKFLOWS.md` for detailed procedures.

---

## Safety First

### Data Integrity
- **Never delete without approval** - Always ask before removing content
- **Preserve everything when merging** - Only remove verified exact duplicates
- **Verify before moving** - Check destination exists, update all `[[wikilinks]]` after
- **Read before writing** - Use Read tool before editing any file

### File Operations
- Use `mv` not `cp` (avoid duplicates)
- Never move numbered folders (00-06) from vault root
- Get approval for bulk operations affecting 5+ files

---

## PARA Structure

```
00_Inbox/       → Temporary capture, process weekly
01_Projects/    → Time-bound work with deadlines
02_Areas/       → Ongoing responsibilities
03_Resources/   → Reference materials
04_Archive/     → Completed items
05_Attachments/ → Media files
06_Metadata/    → Docs & templates
```

**Quick Decision**: Deadline? → Projects | Ongoing? → Areas | Reference? → Resources | Unsure? → Inbox

---

## Git Essentials

```bash
# Always start sessions with
git pull

# After significant work
git add . && git commit -m "vault backup: $(date)" && git push
```

Commit format: `vault backup: YYYY-MM-DD HH:MM:SS`

---

## Memory Integration

Use Memvid MCP for persistent context across sessions:

### Core Workflow
1. **Query first**: Always search memory at task start: `memvid_search`
2. **Work**: Complete task using retrieved context
3. **Write back**: Save decisions: `memvid_add_text` + `memvid_commit`

### What to Store
- **DO**: User preferences, decisions, constraints, patterns, project context
- **DON'T**: Secrets, credentials, errors, logs, temporary data

### Memory File Location
- Default: `.claude/memory/memvid.mv2`
- Project-specific: `.claude/memory/[project-name].mv2`

### Tagging Strategy
Use consistent tags for retrieval:
- `type:preference` - User preferences and settings
- `type:decision` - Architectural and design decisions
- `type:constraint` - Project limitations and requirements
- `type:pattern` - Code patterns and conventions
- `project:[name]` - Project-specific context
- `area:[name]` - Area-specific information

### Quick Reference
```
Search:  memvid_search(query, top_k=5)
Add:     memvid_add_text(content, tags={"type": "decision"})
Commit:  memvid_commit()
List:    memvid_list_contents(limit=20)
Info:    memvid_info()
```

See `06_Metadata/WORKFLOWS.md#memvid-workflows` for detailed procedures.

---

## Note Standards

### Frontmatter
```yaml
---
created: YYYY-MM-DD
modified: YYYY-MM-DD
tags: [specific, tags]
status: draft|active|complete|archived
---
```

### Linking
- Use `[[wikilinks]]` for internal connections
- Link liberally, prefer over-linking
- Check and update links after reorganizing

### Organization
- Inbox is temporary - process weekly
- One idea per note (atomic notes)
- Flat structure over deep nesting (max 3 levels)
- Use links not folders for relationships

---

## Work Approach

**Simple tasks** → Execute directly
**Complex changes** → Propose plan first (affected files, steps, rollback)
**Uncertain info** → Mark `[待确认]` and ask

For bulk operations, provide:
- What's changing and why
- Files affected
- Rollback approach

---

**Detailed workflows, templates, troubleshooting**: → `06_Metadata/WORKFLOWS.md`