claudesidian

To maintain a clean knowledge base, follow these conventions for the 05_Attachments/ directory:

Directory Structure

• 05_Attachments/Organized/: Contains processed files with descriptive names, subdivided into Images/, PDFs/, and Data/.
• 05_Attachments/: The landing zone for unprocessed files (e.g., IMG_*.png, Screenshot*.png, *.pdf).

Naming Standards

• Format: Use YYYY-MM-DD_Descriptive_Name.ext.
• Style: Use underscores (_) instead of spaces. Be descriptive but concise.
• Examples:
  • 2024-03-15_Project_Architecture_Diagram.png
  • API_Documentation_v2.pdf

The 06_Metadata directory serves as the organizational core of the vault, containing documentation, templates, agent configurations, and workflows. It is structured as follows:

• Reference/: Guides, vault documentation, prompt libraries, and style guides.
• Templates/: Standardized note templates (e.g., projects, daily notes, meetings).
• Agents/: Claude Code agent configurations and custom instructions.
• Workflows/: Documented processes and checklists (e.g., weekly reviews, inbox processing).
• Archive/: Old or deprecated configurations.

Claude Code can act as either a research partner or a drafting assistant. Explicitly setting the mode helps guide its behavior.

Setting the Mode (Thinking Mode)

Use this when you want to explore topics without generating new content:

I'm in thinking mode, not writing mode.
Please help me explore [topic] by asking questions
and searching for relevant notes.

Moving to Writing Mode

Use this when you are ready to produce deliverables based on research:

I'm ready to move from thinking to writing mode.
Based on our research in [project], 
help me create an outline for [deliverable].

The vault is organized using the PARA method to manage knowledge effectively:

• 00_Inbox/: Temporary capture point for new ideas.
• 01_Projects/: Active, time-bound initiatives with specific outcomes.
• 02_Areas/: Ongoing responsibilities without an end date (e.g., Health, Finances).
• 03_Resources/: Reference materials and topics of ongoing interest.
• 04_Archive/: Completed projects and inactive items.
• 05_Attachments/: Images, PDFs, and other files.
• 06_Metadata/: Vault configuration and templates.
  • Reference/: Documentation and guides.
  • Templates/: Reusable note templates.
• .scripts/: Helper scripts for automation.

In this system, Areas represent ongoing responsibilities that require continuous attention and have no defined end date. In contrast, Projects are time-bound endeavors with specific completion goals.

Use this distinction to organize your vault:

• Area (Ongoing): "Health", "Finances", "Writing", "Learning", "Clients".
• Project (Time-bound): "Lose 10 pounds by June", "Create 2024 budget", "Finish blog post series", "Complete Python course", "Deliver Project X".

The 04_Archive/ directory is used to store inactive items for future reference. It follows a specific organizational structure to ensure historical data remains accessible:

• Projects_[YEAR]/: Completed projects categorized by year (e.g., Projects_2024/).
• Old_Areas/: Discontinued areas of responsibility.
• Daily_Notes/: Old daily captures.
• Ideas/: Ideas that did not develop into projects.
• Miscellaneous/: All other archived items.

04_Archive/
├── Projects_2024/     # Completed projects by year
├── Projects_2023/
├── Old_Areas/        # Discontinued areas
├── Daily_Notes/      # Old daily captures
├── Ideas/           # Ideas that didn't develop
└── Miscellaneous/   # Everything else

Each Area should follow a consistent folder structure to ensure clarity and ease of use with Claude Code. A standard Area directory includes:

• README.md: Overview and principles of the area.
• Goals/: Current focus areas.
• Resources/: Reference materials.
• Reviews/: Periodic check-ins.
• Ideas/: Future possibilities.

Area_Name/
├── README.md          # Overview and principles
├── Goals/            # Current focus areas
├── Resources/        # Reference materials
├── Reviews/          # Periodic check-ins
└── Ideas/            # Future possibilities

Claude Code can assist in project management (status updates and retrospectives) and learning new topics.

Project Status

Review the project in [folder].
What's the current status?
What are the next actions needed?

Creating a Retrospective

[Project] is now complete.
Review all notes and create a retrospective covering:
- What was accomplished
- Key learnings
- What to do differently next time

Exploring a New Topic

I want to learn about [topic].
Start by searching my vault for any existing knowledge.
Then help me identify what I need to research.

Use these prompts to assess the overall state of your responsibilities and ensure balance across your life.

Health Check

Do a health check on all my areas.
Which have recent activity?
Which have been neglected?

Balance Assessment

Looking at my areas, where am I spending most energy?
What's out of balance?

Integration Opportunities

Find connections between my different areas.
Where could better integration create value?

Leverage Claude Code to find patterns across your notes and synthesize information from specific projects or timeframes.

Finding Connections

Search my vault for anything related to [topic].
What patterns or connections do you see?

Synthesizing a Project

Review all notes in [project folder].
Create a synthesis of the key themes, insights, and open questions.

Weekly Review

Look at all notes created this week.
What are the main themes? 
What connections exist between different projects?

Cross-Project Analysis

Compare insights from [Project A] and [Project B].
What patterns exist across both?
What could each learn from the other?

When starting or ending work sessions with Claude Code in your vault, use specific prompts to maintain continuity and context.

Beginning a Session

Use this to pick up where you left off:

I'm starting work for today. 
Can you review what I was working on yesterday 
and help me pick up where I left off?

Morning Review

To get oriented at the start of the day:

Good morning. Show me:
- Any notes modified yesterday
- Open tasks or questions
- What should I focus on today?

End of Day Wrap-up

To reflect on progress:

End of day review:
- What did I accomplish today?
- What questions or ideas emerged?
- What should I prioritize tomorrow?