vault backup: 2026-01-08 09:34:22

This commit is contained in:
windyboy
2026-01-08 09:34:22 +08:00
parent e967fa874a
commit 0e4d21f721
28 changed files with 3164 additions and 271 deletions
+23
View File
@@ -0,0 +1,23 @@
# Git Workflow
## Session Workflow
```bash
# Always start sessions with
git pull
# After significant work
git add . && git commit -m "vault backup: $(date)" && git push
```
## Commit Format
- Standard: `vault backup: YYYY-MM-DD HH:MM:SS`
- Feature: `feat: description`
- Fix: `fix: description`
- Docs: `docs: description`
## Best Practices
- Pull before starting work
- Commit frequently (after significant changes)
- Push at end of session
- Use descriptive messages for non-backup commits
- Never force push without approval
+19
View File
@@ -0,0 +1,19 @@
# Linking Strategy & Connections
## Core Principles
- Use `[[wikilinks]]` for all internal connections
- Link liberally - prefer over-linking to under-linking
- Always check and update links after reorganizing files
- Proactively suggest connections when relevant
## When to Create Links
- User mentions existing topics/notes
- New content relates to existing knowledge
- Concepts connect across PARA categories
- Creating connections aids discovery
## Link Maintenance
- After moving files, verify all backlinks updated
- Periodically check for broken links
- Suggest creating MOCs (Maps of Content) for clustered topics
- Identify orphaned notes (no connections)
@@ -0,0 +1,24 @@
# PARA Organization System
## Folder Structure
```
00_Inbox/ → Temporary capture, process weekly
01_Projects/ → Time-bound work with deadlines
02_Areas/ → Ongoing responsibilities
03_Resources/ → Reference materials
04_Archive/ → Completed items
05_Attachments/ → Media files
06_Metadata/ → Docs & templates
```
## Quick Decision Tree
- Has deadline? → 01_Projects/
- Ongoing responsibility? → 02_Areas/
- Reference material? → 03_Resources/
- Unsure? → 00_Inbox/
## Organization Principles
- Inbox is temporary - process weekly
- One idea per note (atomic notes)
- Flat structure over deep nesting (max 3 levels)
- Use links not folders for relationships
+17
View File
@@ -0,0 +1,17 @@
# Data Safety & File Operations
## Core Principles
- **Never delete without approval** - Always ask before removing content
- **Preserve everything when merging** - Only remove verified exact duplicates
- **Verify before moving** - Check destination exists, update all `[[wikilinks]]` after
- **Read before writing** - Use Read tool before editing any file
## File Operations
- Use `mv` not `cp` (avoid duplicates)
- Never move numbered folders (00-06) from vault root
- Get approval for bulk operations affecting 5+ files
When proposing bulk operations:
- Explain what's changing and why
- List files affected
- Provide rollback approach
+24
View File
@@ -0,0 +1,24 @@
# Note Standards & Frontmatter
## Required Frontmatter
```yaml
---
created: YYYY-MM-DD
modified: YYYY-MM-DD
tags: [specific, tags]
status: draft|active|complete|archived
---
```
## File Naming
- **Daily notes**: YYYY-MM-DD.md (e.g., 2026-01-08.md)
- **Project notes**: Clear, descriptive names with context
- **Resource notes**: Topic-based naming
- **Avoid**: Special characters except hyphens and underscores
## Note Types
- **Atomic Notes**: Single concept, highly linkable
- **MOCs**: Topic hubs with curated links
- **Daily Notes**: Journal entries, meeting notes, quick captures
- **Project Notes**: Actionable items with clear outcomes
- **Evergreen Notes**: Permanent, well-developed ideas