Skip to content

CLAUDE.md

Latest commit

 

History

History
118 lines (86 loc) · 4.75 KB

CLAUDE.md

File metadata and controls

118 lines (86 loc) · 4.75 KB
Raw

Claude Context File

This file provides context for AI assistants (primarily Claude) working with this Obsidian vault.

Vault Owner

[Your Name] - [Your role/title]. This vault contains [describe what you use it for: work notes, personal projects, learning, etc.].

Work Context (Optional)

[If you use this vault for work, describe your organization and team here]

Personal Context (Optional)

[Describe any personal use cases for this vault]

Key Current Initiatives

[List your current focus areas, projects, or goals]

Vault Structure

vault/
├── .claude/        # Claude commands and configuration
├── inbox/          # Unprocessed items (captures, imports, quick notes)
├── projects/       # Active project briefs and planning
├── ideas/          # Ideas at various stages of development
├── areas/          # Ongoing areas of responsibility
├── resources/      # Reference material, research, learning notes
├── people/         # Contact notes (clients, candidates, partners, colleagues)
├── journal/        # Daily notes, reflections, meetings
├── archive/        # Completed or inactive items
└── templates/      # Note templates

Frontmatter Fields

All notes use YAML frontmatter. Key fields:

Field Purpose
type Note classification: daily, meeting, project, idea, resource, area, person, reflection
status Current state: active, completed, archived, on-hold
summary One-sentence description for AI retrieval (read this first)
tags Topics and themes as array
related Connected notes as [[wikilinks]]
created When the note was created (YYYY-MM-DD)
date When the event happened (for meetings, etc.)

How to Use This Vault

Finding Information

  1. Start with frontmatter: The summary field provides quick context without reading the full note
  2. Use type for filtering: e.g., all type: meeting notes, all type: person notes
  3. Follow related links: These form an explicit knowledge graph
  4. Check status: Focus on active notes for current information

Understanding Context

  • Notes are self-contained: the first paragraph after frontmatter provides full context
  • People are linked as [[people/Name]] - follow these for role and relationship info
  • Projects reference clients in frontmatter

Conventions for AI Interactions

When working with this vault:

  1. Respect existing structure: Follow frontmatter conventions, naming patterns, and folder organization
  2. Prefer editing over creating: Update existing notes rather than creating new ones when possible
  3. Use explicit references: When linking, include context (e.g., "See [[page]] for the full analysis")
  4. Maintain self-contained notes: Each note should be understandable without following links
  5. Add summary to new notes: One sentence that captures the note's purpose

Note Review Standards

When reviewing manually-created notes (via /synapse-review command), check and fix:

Required Frontmatter

Field Required How to Determine
type Always Infer from folder location and content
created Always Use file creation date or today's date
status For actionable notes Default to active for ongoing items
summary Always Generate one-sentence description from content
tags Recommended Extract key themes from content
related If links exist Convert inline [[links]] to frontmatter

Type-Specific Fields

Type Additional Required Fields
meeting date, meeting_type, attendees
person company, role, context
project client (if applicable), phase
idea category, outcome (when decided)

Content Standards

  1. First paragraph: Must be self-contained (who, what, why, relationships)
  2. Links with context: [[page]] should have surrounding explanation
  3. Explicit references: No ambiguous "it", "they", "this" without clear antecedent
  4. Hierarchical headers: H2 for sections, H3 for subsections

When to Ask for Human Input

Request clarification when:

  • Type is ambiguous: Content doesn't clearly fit a single type
  • Status is unclear: Can't determine if item is active, completed, or archived
  • Summary requires interpretation: The note's purpose isn't obvious from content
  • Related notes are uncertain: Potential links exist but relevance is unclear
  • Missing critical context: Names, dates, or relationships that can't be inferred