v2.0: Add hooks, agents, skills, rules, and plugin structure
Major modernization to leverage latest Claude Code features: Plugin Foundation: - Add .claude-plugin/plugin.json manifest for distribution - Add .claude/settings.json with permissions and hooks config Hooks (automatic behaviors): - SessionStart: Initialize vault environment variables - PostToolUse: Auto-commit changes after Write/Edit operations Custom Agents (4): - note-organizer: Vault organization and link maintenance - weekly-reviewer: Facilitate weekly review aligned with goals - goal-aligner: Check daily/weekly alignment with long-term goals - inbox-processor: GTD-style inbox processing Skills (3): - obsidian-vault-ops: Read/write vault files, manage wiki-links - goal-tracking: Track progress across goal cascade - daily-workflow: Morning/midday/evening routines Modular Rules (3): - markdown-standards: File naming, tags, frontmatter conventions - productivity-workflow: Goal cascade, daily/weekly planning - project-management: Project structure and status tracking Other: - Add statusline.sh for terminal vault stats display - Add CLAUDE.local.md.template for personal overrides - Update CLAUDE.md with new features documentation - Update all docs with v2.0 features and upgrade guide 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Bill Allred
108
vault-template/.claude/rules/markdown-standards.md
Normal file
108
vault-template/.claude/rules/markdown-standards.md
Normal file
@@ -0,0 +1,108 @@
|
||||
---
|
||||
paths: "**/*.md"
|
||||
---
|
||||
|
||||
# Markdown Standards for Vault
|
||||
|
||||
These conventions apply to all markdown files in the vault.
|
||||
|
||||
## File Naming
|
||||
|
||||
- **Daily notes:** `YYYY-MM-DD.md` (e.g., `2024-01-15.md`)
|
||||
- **Project folders:** PascalCase (e.g., `MyProject/`)
|
||||
- **General notes:** kebab-case (e.g., `meeting-notes.md`)
|
||||
- **Templates:** Title Case with space (e.g., `Daily Template.md`)
|
||||
|
||||
## Heading Structure
|
||||
|
||||
- H1 (`#`) for note title only - one per file
|
||||
- H2 (`##`) for major sections
|
||||
- H3 (`###`) for subsections
|
||||
- Never skip heading levels (no H1 -> H3)
|
||||
|
||||
## Links
|
||||
|
||||
### Internal Links (Wiki-style)
|
||||
```markdown
|
||||
[[Note Name]] # Link to note
|
||||
[[Note Name|Display Text]] # Link with alias
|
||||
[[Note Name#Section]] # Link to heading
|
||||
[[Folder/Note Name]] # Link with path
|
||||
```
|
||||
|
||||
### External Links
|
||||
```markdown
|
||||
[Display Text](https://url.com)
|
||||
```
|
||||
|
||||
## Tags
|
||||
|
||||
### Standard Tag Hierarchy
|
||||
```
|
||||
#priority/high
|
||||
#priority/medium
|
||||
#priority/low
|
||||
|
||||
#status/active
|
||||
#status/waiting
|
||||
#status/completed
|
||||
#status/archived
|
||||
|
||||
#context/work
|
||||
#context/personal
|
||||
#context/health
|
||||
#context/learning
|
||||
#context/family
|
||||
```
|
||||
|
||||
### Tag Placement
|
||||
- In YAML frontmatter: `tags: [tag1, tag2]`
|
||||
- Inline: at end of relevant line or paragraph
|
||||
|
||||
## Task Format
|
||||
|
||||
```markdown
|
||||
- [ ] Incomplete task
|
||||
- [x] Completed task
|
||||
- [ ] Task with context #work @home
|
||||
- [ ] Task with due date 📅 2024-01-20
|
||||
```
|
||||
|
||||
## YAML Frontmatter
|
||||
|
||||
All notes should include frontmatter:
|
||||
```yaml
|
||||
---
|
||||
date: YYYY-MM-DD
|
||||
tags: [relevant, tags]
|
||||
status: active|completed|archived
|
||||
---
|
||||
```
|
||||
|
||||
## Text Formatting
|
||||
|
||||
- **Bold** for emphasis and key terms
|
||||
- *Italic* for subtle emphasis
|
||||
- `Code` for commands, paths, technical terms
|
||||
- > Blockquotes for important callouts
|
||||
|
||||
## Lists
|
||||
|
||||
- Use `-` for unordered lists
|
||||
- Use `1.` for ordered lists
|
||||
- Indent with 2 spaces for nested items
|
||||
|
||||
## Code Blocks
|
||||
|
||||
Use fenced code blocks with language:
|
||||
```javascript
|
||||
const example = "code";
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. One idea per paragraph
|
||||
2. Use blank lines between sections
|
||||
3. Keep lines under 100 characters when possible
|
||||
4. Include links to related notes
|
||||
5. Add meaningful frontmatter
|
||||
123
vault-template/.claude/rules/productivity-workflow.md
Normal file
123
vault-template/.claude/rules/productivity-workflow.md
Normal file
@@ -0,0 +1,123 @@
|
||||
---
|
||||
paths: "Goals/**/*.md, Daily Notes/**/*.md"
|
||||
---
|
||||
|
||||
# Productivity Workflow Rules
|
||||
|
||||
These conventions apply to goal files and daily notes.
|
||||
|
||||
## Goal Cascade Principle
|
||||
|
||||
Goals flow from long-term vision to daily actions:
|
||||
```
|
||||
3-Year Vision (life direction)
|
||||
→ Yearly Goals (annual objectives)
|
||||
→ Monthly Goals (current focus)
|
||||
→ Weekly Review (this week's plan)
|
||||
→ Daily Tasks (today's actions)
|
||||
```
|
||||
|
||||
## Goal Setting Standards
|
||||
|
||||
### SMART Goals
|
||||
Every goal should be:
|
||||
- **S**pecific - Clear and well-defined
|
||||
- **M**easurable - Has quantifiable outcomes
|
||||
- **A**chievable - Realistic given constraints
|
||||
- **R**elevant - Aligned with higher-level goals
|
||||
- **T**ime-bound - Has a deadline
|
||||
|
||||
### Goal Limits
|
||||
- Maximum 3 active high-priority goals at once
|
||||
- Each goal should have clear success criteria
|
||||
- Goals without action in 14+ days need review
|
||||
|
||||
## Daily Planning Rules
|
||||
|
||||
### Morning (5 minutes)
|
||||
1. Create daily note or open existing
|
||||
2. Identify ONE Big Thing for the day
|
||||
3. Review yesterday's incomplete tasks
|
||||
4. Set realistic time blocks
|
||||
|
||||
### The ONE Thing
|
||||
> "What's the ONE thing I can do today such that by doing it everything else will be easier or unnecessary?"
|
||||
|
||||
Always answer this question in the Focus section.
|
||||
|
||||
### Task Prioritization
|
||||
1. Must Do Today - Non-negotiable, deadline-driven
|
||||
2. Should Do - Important but flexible timing
|
||||
3. Could Do - Nice to have if time permits
|
||||
4. Won't Do - Explicitly dropped (acknowledge trade-offs)
|
||||
|
||||
## Weekly Review Rules
|
||||
|
||||
### When: Sunday or Monday
|
||||
### Duration: 30 minutes minimum
|
||||
|
||||
### Required Elements
|
||||
1. **Collect** - Gather all loose ends
|
||||
2. **Process** - Decide on each item
|
||||
3. **Review** - Check goal progress
|
||||
4. **Plan** - Set next week's priorities
|
||||
|
||||
### Checklist
|
||||
- [ ] All inboxes emptied
|
||||
- [ ] All daily notes from week reviewed
|
||||
- [ ] Goal progress calculated
|
||||
- [ ] Next week's ONE Big Thing identified
|
||||
- [ ] Calendar reviewed for commitments
|
||||
|
||||
## Progress Tracking
|
||||
|
||||
### Checkbox Format
|
||||
```markdown
|
||||
- [ ] Not started
|
||||
- [/] In progress (optional)
|
||||
- [x] Completed
|
||||
```
|
||||
|
||||
### Percentage Updates
|
||||
Update percentages when progress is made:
|
||||
```markdown
|
||||
- [ ] Learn Spanish (25% → 30%)
|
||||
```
|
||||
|
||||
### Milestone Dates
|
||||
Record significant progress:
|
||||
```markdown
|
||||
- [x] Complete course Module 1 ✓ 2024-01-15
|
||||
```
|
||||
|
||||
## Time Management
|
||||
|
||||
### Time Blocks
|
||||
Structure days around energy:
|
||||
- 🌅 Morning: High-focus work (9-12)
|
||||
- ☀️ Afternoon: Meetings, admin (12-5)
|
||||
- 🌙 Evening: Light tasks, learning (5+)
|
||||
|
||||
### Energy Tracking
|
||||
Log energy levels daily (1-10):
|
||||
```markdown
|
||||
**Energy:** 7/10 - Good morning, afternoon slump
|
||||
```
|
||||
|
||||
## Archive Rules
|
||||
|
||||
Move to Archives when:
|
||||
- Project completed
|
||||
- Goal achieved or abandoned
|
||||
- Daily notes older than 30 days (optional)
|
||||
|
||||
Archive format:
|
||||
```
|
||||
Archives/
|
||||
├── Projects/
|
||||
│ └── Completed-Project-2024/
|
||||
├── Goals/
|
||||
│ └── 2023-Goals.md
|
||||
└── Daily Notes/
|
||||
└── 2024-01/
|
||||
```
|
||||
137
vault-template/.claude/rules/project-management.md
Normal file
137
vault-template/.claude/rules/project-management.md
Normal file
@@ -0,0 +1,137 @@
|
||||
---
|
||||
paths: "Projects/**/*.md"
|
||||
---
|
||||
|
||||
# Project Management Rules
|
||||
|
||||
These conventions apply to project folders and documentation.
|
||||
|
||||
## Project Structure
|
||||
|
||||
Each project gets its own folder:
|
||||
```
|
||||
Projects/
|
||||
└── Project-Name/
|
||||
├── CLAUDE.md # Required: Project context for AI
|
||||
├── README.md # Optional: Overview if complex
|
||||
├── notes/ # Optional: Related notes
|
||||
└── resources/ # Optional: Reference materials
|
||||
```
|
||||
|
||||
## Project CLAUDE.md
|
||||
|
||||
Every project must have a CLAUDE.md file with:
|
||||
|
||||
```markdown
|
||||
# Project: [Name]
|
||||
|
||||
## Overview
|
||||
[1-2 sentence description of what this project is]
|
||||
|
||||
## Status
|
||||
- **Phase:** Planning | Active | On Hold | Complete
|
||||
- **Progress:** X%
|
||||
- **Started:** YYYY-MM-DD
|
||||
- **Target:** YYYY-MM-DD
|
||||
|
||||
## Goals
|
||||
What success looks like for this project.
|
||||
|
||||
## Current Focus
|
||||
What I'm actively working on right now.
|
||||
|
||||
## Key Decisions
|
||||
Important decisions made and their rationale.
|
||||
|
||||
## Next Actions
|
||||
- [ ] Immediate next step
|
||||
- [ ] Following step
|
||||
|
||||
## Blockers
|
||||
Anything preventing progress.
|
||||
|
||||
## Resources
|
||||
- [[Related Note]]
|
||||
- [External Link](url)
|
||||
|
||||
## Notes for Claude
|
||||
[Any specific context Claude should know when helping with this project]
|
||||
```
|
||||
|
||||
## Project Status Values
|
||||
|
||||
Use consistent status labels:
|
||||
- `Planning` - Defining scope and approach
|
||||
- `Active` - Currently being worked on
|
||||
- `On Hold` - Temporarily paused (note reason)
|
||||
- `Blocked` - Waiting on external dependency
|
||||
- `Review` - Work complete, needs review
|
||||
- `Complete` - Done and ready for archive
|
||||
|
||||
## Progress Tracking
|
||||
|
||||
### Percentage Guidelines
|
||||
- 0-10%: Planning and setup
|
||||
- 10-30%: Initial implementation
|
||||
- 30-70%: Core work
|
||||
- 70-90%: Refinement and polish
|
||||
- 90-100%: Final review and completion
|
||||
|
||||
### Update Frequency
|
||||
- Update progress weekly at minimum
|
||||
- Update status when it changes
|
||||
- Update blockers immediately
|
||||
|
||||
## Linking Projects
|
||||
|
||||
### To Goals
|
||||
Link projects to their parent goals:
|
||||
```markdown
|
||||
**Supports:** [[1. Yearly Goals#Goal Name]]
|
||||
```
|
||||
|
||||
### To Daily Notes
|
||||
Reference project work in daily notes:
|
||||
```markdown
|
||||
## Work Log
|
||||
- Worked on [[Project Name]] - completed X
|
||||
```
|
||||
|
||||
### Between Projects
|
||||
Link related projects:
|
||||
```markdown
|
||||
**Related:** [[Other Project]]
|
||||
```
|
||||
|
||||
## Project Lifecycle
|
||||
|
||||
### Starting a Project
|
||||
1. Create folder in `Projects/`
|
||||
2. Create CLAUDE.md from template
|
||||
3. Link to relevant goal
|
||||
4. Define first next action
|
||||
5. Set target completion date
|
||||
|
||||
### During Project
|
||||
1. Update CLAUDE.md with progress
|
||||
2. Log work in daily notes
|
||||
3. Capture decisions and rationale
|
||||
4. Track blockers immediately
|
||||
5. Adjust timeline if needed
|
||||
|
||||
### Completing a Project
|
||||
1. Update status to Complete
|
||||
2. Add completion date and summary
|
||||
3. Document lessons learned
|
||||
4. Move folder to Archives/Projects/
|
||||
5. Update goal progress
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. Keep project scope realistic
|
||||
2. One primary focus at a time
|
||||
3. Break large projects into phases
|
||||
4. Review all active projects weekly
|
||||
5. Archive completed projects promptly
|
||||
6. Document decisions as they're made
|
||||
7. Link to relevant context liberally
|
||||
Reference in New Issue
Block a user