78a822a3df
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>
2.1 KiB
2.1 KiB
paths
| 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)
[[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
[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
- [ ] Incomplete task
- [x] Completed task
- [ ] Task with context #work @home
- [ ] Task with due date 📅 2024-01-20
YAML Frontmatter
All notes should include frontmatter:
---
date: YYYY-MM-DD
tags: [relevant, tags]
status: active|completed|archived
---
Text Formatting
- Bold for emphasis and key terms
- Italic for subtle emphasis
Codefor 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:
const example = "code";
Best Practices
- One idea per paragraph
- Use blank lines between sections
- Keep lines under 100 characters when possible
- Include links to related notes
- Add meaningful frontmatter