promptsDBText Analysis & GenerationProductivityOrganization
Organize Digital Files (Folder Structure)
Produce an ASCII three-level folder structure with placeholders, naming conventions, archive/retention rules, and migration steps, customized to your file types, organization method, and special requirements.
Prompt Content
Create a concise, implementable folder structure plan for my digital files.
Use my inputs:
- File types:
<file-types>
File Types
</file-types>
- Preferred organization method: Organization Method
- Special requirements:
<special-requirements>
Special Requirements
</special-requirements>
Produce exactly these sections:
1) Summary (1 sentence).
2) Folder Tree (max 3 levels). Use an ASCII tree. Include reusable placeholders in braces, e.g., {client}, {project}, {year}. Keep 5-12 top-level folders.
3) Naming Rules (5-7 bullets).
4) Archive & Retention (3-5 bullets).
5) Migration Steps (5-8 numbered steps).
Constraints:
• Plain text only
• Use clear, logical grouping aligned to the stated method
• Prefer consistent prefixes (e.g., 01-, 02-) for ordered folders
• File/folder names: kebab-case, no spaces or special characters, max ~60 chars
• Dates: YYYY or YYYY-MM-DD when relevant
• Versions: v01, v02, ...
• Propose umbrella categories when inputs are overlapping
<example>
Folder Tree (example):
/
├─ 00-admin
├─ clients
│ ├─ {client}
│ │ ├─ {project}
│ │ │ ├─ 01-planning
│ │ │ ├─ 02-assets
│ │ │ ├─ 03-deliverables
│ │ │ └─ 99-archive
├─ templates
└─ archive
Naming Rules (example):
• kebab-case-only
• Optional date prefix: YYYY-MM-DD
• Version suffix: v01
File name example: acme-website-homepage-2025-03-14-v02.png
</example>
Variables
- File Types
- List the file types/categories you have and notable examples or extensions.
- Example: photos (RAW, JPEG), video (MP4), design (PSD, AI), invoices (PDF), contracts (DOCX), meeting notes (TXT)
- Organization Method
- How you prefer to organize (e.g., by client, project, date, department, topic, or a hybrid path).
- Example: client > project > phase (with yearly archive)
- Special Requirements
- Constraints or preferences like personal vs team, tools/platforms, naming conventions, retention/privacy rules, scale, or any must/avoid notes.
- Example: Team of 8; Windows + OneDrive; keep legal docs 7 years; short names; avoid spaces; include versioning.