Initial commit - Claudesidian v0.2.0

Claude Code + Obsidian starter kit for AI-powered knowledge management.

Features:
- PARA method folder structure
- Bootstrap initialization system
- Pre-configured Claude Code commands and agents
- Gemini Vision MCP server with video support
- Helper scripts for vault management
- Automated release management

See README.md for setup instructions.
This commit is contained in:
Noah Brier
2025-09-13 12:20:50 -04:00
commit f609668172
45 changed files with 4776 additions and 0 deletions
+136
View File
@@ -0,0 +1,136 @@
# 🔄 Areas
Ongoing responsibilities and spheres of activity you maintain over time.
## Purpose
Areas are **ongoing responsibilities** that:
- Have no end date
- Require continuous attention
- Define your roles and commitments
- Need regular maintenance
## What Belongs Here
### Personal Areas
- Health & Fitness
- Finances
- Relationships
- Personal Development
- Home & Environment
### Professional Areas
- Team Management
- Client Relationships
- Professional Skills
- Industry Knowledge
- Networking
### Creative Areas
- Writing Practice
- Content Creation
- Learning & Research
- Side Projects
## Area Structure
Each area might contain:
```
Area_Name/
├── README.md # Overview and principles
├── Goals/ # Current focus areas
├── Resources/ # Reference materials
├── Reviews/ # Periodic check-ins
└── Ideas/ # Future possibilities
```
## Claude Code Workflows
### Area Review
```
Review my [area name] area.
What patterns do you see in recent notes?
What aspects need more attention?
```
### Setting Goals
```
Help me set quarterly goals for [area].
Based on recent activity, what should I prioritize?
```
### Finding Gaps
```
Analyze my [area] notes.
What important topics am I not tracking?
What questions should I be asking?
```
### Cross-Area Analysis
```
Compare my [Area A] and [Area B] notes.
Where do they overlap?
How might they inform each other?
```
## Area vs Project
**Ask yourself**: Does this have an end date?
| Area (Ongoing) | Project (Time-bound) |
|---------------|---------------------|
| "Health" | "Lose 10 pounds by June" |
| "Finances" | "Create 2024 budget" |
| "Writing" | "Finish blog post series" |
| "Learning" | "Complete Python course" |
| "Clients" | "Deliver Project X" |
## Maintenance Practices
### Weekly
- Quick scan of each area
- Note any urgent needs
- Capture new ideas
### Monthly
- Review goals and progress
- Update resource lists
- Clean up old notes
### Quarterly
- Deep review with Claude Code
- Adjust focus areas
- Archive outdated material
## Claude Code Prompts
### 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?
```
## Tips
- **Areas inform Projects** - Projects often emerge from area needs
- **Keep them active** - Dead areas should be archived
- **Review regularly** - Areas drift without attention
- **Document standards** - What does "good" look like?
- **Track metrics** - Even qualitative areas benefit from measurement
## Remember
Areas are the backdrop of your life. They don't complete, but they evolve. Use Claude Code to help you see patterns and maintain balance across all your responsibilities.