Home
cd ../playbooks
File OrganizationAdvanced

Smart File Organizer

Organize and rename files based on content analysis

10 minutes
By communitySource
#file#organization#naming#structure

Your files are named IMG_4023.jpg, Document(1).pdf, and final_FINAL_v3_USE_THIS.docx. You can't find anything without searching, and searching doesn't work because nothing is named sensibly. Your folder structure was 'temporary' three years ago.

Who it's for: anyone with thousands of poorly named files, photographers organizing years of photos, professionals reorganizing project archives, teams standardizing shared drive structures, people migrating files between systems who want clean organization

Example

"Organize my project files into a sensible structure" → Files analyzed by content and metadata, renamed with consistent conventions (date-project-description), sorted into logical folders, and a before/after report showing what moved where

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

# File Organizer

Intelligently organize and rename files based on their content and metadata.

## Overview

This workflow helps you:
- Analyze file contents to determine categorization
- Suggest folder structures
- Generate consistent naming conventions
- Identify and handle duplicates
- Create organization systems

## How to Use

### Analyze Files
```
"Analyze these files and suggest how to organize them"
"What category does this file belong to?"
"Suggest a better filename for this document"
```

### Organize
```
"Create a folder structure for my project files"
"Organize my downloads folder"
"Sort these invoices by vendor and date"
```

## Naming Conventions

### Recommended Formats

**Documents**
```
YYYY-MM-DD_Category_Description_v1.ext
Example: 2026-01-29_Contract_ClientName_NDA_v1.pdf
```

**Images**
```
YYYY-MM-DD_Event/Project_Description_NNN.ext
Example: 2026-01-29_ProductLaunch_HeroImage_001.png
```

**Invoices/Receipts**
```
YYYY-MM-DD_Vendor_Amount_InvoiceNumber.ext
Example: 2026-01-29_Adobe_149.99_INV-12345.pdf
```

**Meeting Notes**
```
YYYY-MM-DD_MeetingType_Topic.ext
Example: 2026-01-29_TeamSync_Q1Planning.md
```

### Naming Rules
- Use underscores or hyphens, not spaces
- Start with date for chronological sorting
- Include key identifiers (client, project, type)
- Add version numbers for iterations
- Keep names concise but descriptive

## Folder Structures

### Personal Documents
```
šŸ“ Documents
ā”œā”€ā”€ šŸ“ Admin
│   ā”œā”€ā”€ šŸ“ Finance
│   │   ā”œā”€ā”€ šŸ“ Invoices
│   │   ā”œā”€ā”€ šŸ“ Receipts
│   │   └── šŸ“ Tax
│   ā”œā”€ā”€ šŸ“ Insurance
│   └── šŸ“ Legal
ā”œā”€ā”€ šŸ“ Work
│   ā”œā”€ā”€ šŸ“ Projects
│   ā”œā”€ā”€ šŸ“ Reports
│   └── šŸ“ Meetings
ā”œā”€ā”€ šŸ“ Personal
│   ā”œā”€ā”€ šŸ“ Health
│   ā”œā”€ā”€ šŸ“ Education
│   └── šŸ“ Travel
└── šŸ“ Archive
    └── šŸ“ [Year]
```

### Project-Based
```
šŸ“ ProjectName
ā”œā”€ā”€ šŸ“ 01_Planning
│   ā”œā”€ā”€ šŸ“ Requirements
│   ā”œā”€ā”€ šŸ“ Proposals
│   └── šŸ“ Research
ā”œā”€ā”€ šŸ“ 02_Design
│   ā”œā”€ā”€ šŸ“ Mockups
│   ā”œā”€ā”€ šŸ“ Assets
│   └── šŸ“ Specs
ā”œā”€ā”€ šŸ“ 03_Development
│   ā”œā”€ā”€ šŸ“ Source
│   ā”œā”€ā”€ šŸ“ Tests
│   └── šŸ“ Documentation
ā”œā”€ā”€ šŸ“ 04_Deliverables
│   └── šŸ“ [Version]
ā”œā”€ā”€ šŸ“ 05_Admin
│   ā”œā”€ā”€ šŸ“ Contracts
│   ā”œā”€ā”€ šŸ“ Invoices
│   └── šŸ“ Communications
└── šŸ“ Archive
```

### Client/Vendor
```
šŸ“ Clients
└── šŸ“ [ClientName]
    ā”œā”€ā”€ šŸ“ Contracts
    ā”œā”€ā”€ šŸ“ Projects
    │   └── šŸ“ [ProjectName]
    ā”œā”€ā”€ šŸ“ Invoices
    ā”œā”€ā”€ šŸ“ Communications
    └── šŸ“ Assets
```

## Output Formats

### Organization Plan
```markdown
## File Organization Plan

**Source**: [Folder/Location]
**Total Files**: [Count]
**Total Size**: [Size]

### Proposed Structure
[Folder tree]

### File Mapping
| Original Name | New Name | Destination |
|--------------|----------|-------------|
| IMG_1234.jpg | 2026-01-29_ProductPhoto_001.jpg | /Products/Photos/ |
| doc1.pdf | 2026-01-15_Contract_ClientA_NDA.pdf | /Clients/ClientA/Contracts/ |

### Actions Required
1. Create folders: [list]
2. Rename files: [count]
3. Move files: [count]
4. Review manually: [count with reasons]
```

### Duplicate Report
```markdown
## Duplicate Files Report

**Total Duplicates Found**: [Count]
**Space Recoverable**: [Size]

### Exact Duplicates
| File | Locations | Size | Recommendation |
|------|-----------|------|----------------|
| report.pdf | /Downloads/, /Documents/ | 2.3MB | Keep in /Documents/ |

### Similar Files
| Files | Similarity | Difference |
|-------|------------|------------|
| report_v1.pdf, report_v2.pdf | 95% | v2 has extra page |
```

## Analysis Capabilities

### Content-Based Categorization
- **Documents**: Contracts, reports, letters, forms
- **Financial**: Invoices, receipts, statements, budgets
- **Media**: Photos, videos, audio, graphics
- **Code**: Source files, configs, documentation
- **Data**: Spreadsheets, databases, exports

### Metadata Extraction
- Creation/modification dates
- Author information
- File dimensions (images/video)
- Duration (audio/video)
- Page count (documents)

## Automation Rules

### Example Rules
```markdown
## Auto-Organization Rules

### Rule 1: Invoices
- Trigger: PDF with "Invoice" or "INV-" in content
- Action: Move to /Finance/Invoices/[Year]/[Month]/
- Rename: YYYY-MM-DD_Vendor_Amount.pdf

### Rule 2: Screenshots
- Trigger: File matches "Screenshot*.png"
- Action: Move to /Screenshots/[Year-Month]/
- Rename: YYYY-MM-DD_HH-MM_Screenshot.png

### Rule 3: Downloads Cleanup
- Trigger: File in Downloads older than 30 days
- Action: 
  - If document → Archive
  - If installer → Delete
  - If media → Sort to appropriate folder
```

## Best Practices

### Organization Principles
1. **PARA Method**: Projects, Areas, Resources, Archive
2. **Date-First**: Enables chronological sorting
3. **Descriptive Names**: Future you will thank you
4. **Flat is Better**: Avoid deep nesting (max 3-4 levels)
5. **Regular Maintenance**: Schedule monthly reviews

### File Hygiene
- Delete duplicates and temp files
- Archive completed projects
- Use cloud sync for important files
- Maintain consistent naming
- Document your system

## Limitations

- Cannot access protected/encrypted files
- Large file moves require manual execution
- Content analysis depends on file format support
- Cannot guarantee perfect categorization
- Manual review recommended for important files
README.md

What This Does

Intelligently organize and rename files based on their content and metadata.


Quick Start

Step 1: Create a Project Folder

mkdir -p ~/Documents/FileOrganizer

Step 2: Download the Template

Click Download above, then:

mv ~/Downloads/CLAUDE.md ~/Documents/FileOrganizer/

Step 3: Start Working

cd ~/Documents/FileOrganizer
claude

How to Use

Analyze Files

Organize

Output Format

Organization Plan

Best Practices

Organization Principles

  1. PARA Method: Projects, Areas, Resources, Archive
  2. Date-First: Enables chronological sorting
  3. Descriptive Names: Future you will thank you
  4. Flat is Better: Avoid deep nesting (max 3-4 levels)
  5. Regular Maintenance: Schedule monthly reviews

File Hygiene

  • Delete duplicates and temp files
  • Archive completed projects
  • Use cloud sync for important files
  • Maintain consistent naming
  • Document your system

Limitations

  • Cannot access protected/encrypted files
  • Large file moves require manual execution
  • Content analysis depends on file format support
  • Cannot guarantee perfect categorization
  • Manual review recommended for important files

$Related Playbooks