---
tags:
  - prompting
  - obsidian
  - llm
---
# Organize your notes with Claude Code

Here’s what Claude Code did for me:

- Researched best practices for note organization
- Suggested the most effective method tailored to my structure
- Tagged all my notes, created templates, added missing tags in two languages, and even built MOCs (Maps of Content)

``` markdown

## Instructions

You will analyze the provided knowledge base structure and notes to create an improved organizational system. Follow these steps:

### Phase 1: Analysis

First, examine the current structure inside `<analysis>` tags:

**Current Organization Assessment**
- Identify the organizational method (folders, tags, links, or combination)- Note any patterns in naming conventions- Assess the depth of folder hierarchy- Identify potential information silos or duplicated content- Check for orphaned notes or broken connections

**Content Type Classification**
- Categorize the types of notes present (reference, project, personal, etc.)- Identify recurring themes or topics- Note the average length and complexity of notes- Determine if notes follow atomic principles or contain multiple concepts

**Usage Pattern Recognition**
- Identify how notes connect to each other- Assess the current linking strategy- Determine primary use cases (research, projects, learning, etc.)

### Phase 2: Recommendations

Based on your analysis, provide detailed recommendations inside `<recommendations>` tags:

1. **Organizational Structure**

Choose the most appropriate primary method:

- **Flat structure with MOCs** (Maps of Content) for maximum flexibility
- **PARA method** (Projects, Areas, Resources, Archive) for action-oriented systems
- **Hybrid approach** combining minimal folders with extensive linking
- Justify your choice based on the user's content and patterns

2. **Note Architecture**

Recommend note types:

- **Atomic notes** for single concepts
- **MOC notes** for topic organization
- **Index notes** for navigation
- **Daily notes** for capturing fleeting thoughts

Provide templates for each recommended note type

3. **Metadata and Tagging System**

- Design a hierarchical tag structure using nested tags (e.g., #type/article, #status/draft)
- Recommend YAML frontmatter properties for enhanced organization
- Suggest tag categories: content type, status, topic, source

3. **Linking Strategy**

- Establish linking conventions
- Recommend when to use links vs. tags
- Suggest MOC creation triggers (e.g., when a topic has 5+ related notes)

3. **Search and Retrieval Optimization**
- Recommend naming conventions for better search
- Suggest Dataview queries for dynamic organization
- Provide search operators for efficient retrieval

### Phase 3: Implementation Plan

Provide a step-by-step migration plan inside `<implementation>` tags:

**Preparation Phase** (Week 1)
- Backup current vault
- Install recommended plugins
- Create folder structure and initial MOCs

**Migration Phase** (Weeks 2-3)
- Prioritize notes for migration- Update note formats and add metadata- Create connections and MOCs

**Optimization Phase** (Week 4)
- Review and refine the system- Create documentation for future reference- Establish maintenance routines

### Phase 4: Practical Examples

Inside `<examples>` tags, provide:

**Before and after** examples of note organization
**Sample MOC structure** with Dataview queries
**Template examples** for different note types
**Example tag hierarchy** specific to their content

### Important Principles to Apply:
- **Future-proof design**: Create a system that scales with growth
- **Low-friction capture**: Ensure quick note creation without complex categorization
- **Progressive organization**: Start simple, add complexity as needed
- **Cross-referencing**: Maximize connections between related concepts
- **Regular maintenance**: Include periodic review processes

Remember to:
- Prioritize findability over perfect categorization
- Design for the user's "worst day" when they're tired or rushed
- Balance structure with flexibility
- Incorporate both explicit (folders/tags) and implicit (links) organization
- Consider AI-assisted search capabilities in modern tools

Your final output should be practical, actionable, and tailored to the specific content and usage patterns identified in the user's current system.
```