You point Claude at a folder and paste one paragraph. You do not need to be technical, but you do need the right Claude to do it.
Open Claude Code in the messy folder, then paste this exactly.
Go through every file in this folder and organise it the way a tidy, organised
person would. Use your judgment to work out what each file is and where it should
sensibly live, then create clearly named folders and move everything into them.
If you are not sure where something belongs, ask me before you move it. If you
still can't tell, put it in a folder called "review me" so I can check it myself.
Don't delete anything, and don't dump files into random folders, build a structure
that actually makes sense.Most file-sorting prompts just say "sort by type," and you end up with folders that still do not help you find anything. This one tells Claude to think like an organised person, ask when it is unsure, and park the maybes in a single review folder. That is the difference between a one-time cleanup and a system you would actually keep using.
Once your structure exists, keep it clean with a shorter version. Run this whenever a project finishes or the folder gets messy again.
Organise this folder the same way as before: use your judgment, ask me about
anything ambiguous, put the maybes in a folder called "review me", and don't
delete anything.Once the big cleanup is done, these keep everything tidy. Same rules apply: point Claude Code at the folder, and it only ever moves or renames, never deletes.
Look through this folder for files with useless names like IMG_4821, Untitled 3,
Screenshot 2026-01-02, and document(final)(2). For each one, work out what it
actually is from its contents, type, and date, then rename it to something clear
and consistent, like 2026-01-15-invoice-figma.pdf or client-logo-final.png. Keep a
plain-text log mapping every old name to its new name so I can undo it, and don't
delete or move anything, only rename.My desktop is my dumping ground. Move everything on it into a folder called Desktop
Archive, sorted into sensible subfolders by type and project, except for the handful
of things I clearly use every day, which you should leave in a small folder called
Active. Ask me if you are unsure whether something is active. Don't delete anything,
just get my actual desktop to nearly empty while keeping everything findable.Scan this folder and its subfolders for files that are exact duplicates or very
likely the same thing (same content, or near-identical names and sizes like
report.pdf and report(1).pdf). Do not delete anything. Instead give me a simple list
grouped by which files look like copies of each other, with the full path of each,
and mark which one you would keep. I will decide what to remove.Organise this folder of documents (PDFs, docs, invoices, contracts) into a filing
system a tidy person would build: clear top-level folders by area, sensible
subfolders, and consistent names with dates. Then create an index file at the top
that lists what lives where and where new things should go, so the system is obvious
later. Ask me about anything ambiguous, put maybes in review me, and don't delete
anything.Based on how the files in this folder are actually used, propose one simple naming
convention and folder structure I can stick to going forward (for example
date-project-description). Explain the rule in a few plain lines, then save it as a
README file in this folder, and rename or move a few example files to show me what
it looks like in practice. Keep it simple enough that I will actually follow it.🤖 Claude Code: claude.com/product/claude-code (needs a paid plan) · 💻 VS Code: code.visualstudio.com (free)