Files
my-vault/05_Attachments/README.md
T
windyboy 8e3943f064 Initial vault setup with PARA structure
- Created CLAUDE.md configuration file
- Created WEEKLY_REVIEW.md template
- Set up PARA folder structure (Projects, Areas, Resources, Archive)
- Created README files for each main folder
- Configured .gitignore for vault files
- Saved vault configuration to .claude/vault-config.json

Generated with Claude Code
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 21:10:11 +08:00

40 lines
1.1 KiB
Markdown

# Attachments
**Purpose:** Storage for all non-text files (images, PDFs, videos, audio).
## Organization
- **Root (05_Attachments/)** - Unprocessed attachments
- **Organized/** - Files that have been properly named and referenced
## Naming Convention
Use descriptive names that indicate the related note:
- `[RelatedNote]_[Description].[ext]`
- Example: `ProjectAlpha_Architecture_Diagram.png`
- Example: `BookNotes_Thinking_Fast_Slow_Cover.jpg`
## Helper Scripts
```bash
pnpm attachments:list # List unprocessed files
pnpm attachments:organized # Count organized files
pnpm attachments:orphans # Find unreferenced files
pnpm attachments:update-links # Update links after moving
```
## Processing Workflow
1. Files initially land in `05_Attachments/`
2. Rename with descriptive names
3. Reference in notes using `![[filename.ext]]`
4. Move to `Organized/` subfolder
5. Update any links if paths change
## Tips
- Process attachments regularly (don't let them pile up)
- Use consistent naming patterns
- Delete duplicates and unused files
- Consider using Gemini Vision to analyze images