| name | file-organizer |
| description | Suggest file naming conventions, folder structures, and organization strategies |
| tags | ["organization","files","naming","structure","productivity"] |
| author | L.I.N.K. |
| version | 1.0.0 |
File Organizer Skill
When the user shares a messy directory listing, asks for naming conventions, or mentions file clutter:
Capabilities
- Folder Structure — Design hierarchical directories by project, date, type, or client
- Naming Conventions — Create consistent, searchable, sortable file names
- Version Control — Recommend versioning patterns (v1, v2, YYYYMMDD)
- Cleanup Strategy — Identify duplicates, old files, and orphaned assets
- Metadata Tagging — Suggest tags, prefixes, or suffixes for discoverability
- Migration Plan — Step-by-step reorganization that preserves references
Principles
- Searchable — Can find files without remembering exact locations
- Sortable — Files appear in logical order by default
- Self-documenting — File names explain contents without opening them
- Future-proof — Works even when projects scale to hundreds of files
Response Format
## Recommended Structure
project/
├── 00-planning/
│ ├── 2024-01-15-brief.md
│ └── 2024-01-20-requirements.md
├── 01-design/
│ ├── 2024-02-v1-wireframes.fig
│ └── 2024-02-v2-wireframes.fig
├── 02-development/
│ └── ...
├── 99-archive/
│ └── [Old versions, superseded files]
└── README.md
## Naming Convention
[YYYY-MM-DD]-[project]-[type]-[version].[ext]
Example: 2024-05-01-jarvis-skill-v2.md
## Files to Move / Rename
| Current Path | Suggested Path | Action |
|--------------|----------------|--------|
| `doc1.pdf` | `01-design/2024-01-10-brand-guidelines.pdf` | Rename + Move |
## Files to Archive / Delete
- [Old temp files, duplicates]
## Migration Steps
1. [Step-by-step, safe reorganization]
Always prioritize safety — suggest backing up before bulk renaming or moving files.
