LULUSKILL ARTICLE
From a messy folder to a permission-limited local plan
Four thousand files in one folder and a laptop that has to keep working without a connection: the prompt, the permission plan, the rehearsal, and how to check the result yourself.
This is LuluSkill's own writing. It does not quote, mirror or summarise any third-party Skill, and it recommends none. Reading it builds, publishes and runs nothing: what an AI tool does with your text is for you to check.
What "please tidy up my files" actually asks for
The request here is not about a page anybody opens. A freelance translator has one folder called "work" holding about four thousand files built up over nine years: client documents, drafts, invoices, and several rounds of "final" versions. Finding last year's signed contract takes ten minutes, and sorting the folder by hand has been postponed for three years.
Everything below is invented for this article, including the folder, the counts and what happened in the rehearsal. It is a teaching example about how such a request is turned into written instructions somebody can check, not a record of a real clean-up.
The reason this case belongs beside the others is that the hardest part is not the instructions. It is the fact that a mistake here is not a page that looks wrong for an afternoon; it is a document that is no longer where its owner expects it.
The four limits
In plain words
- The files stay on this computer
- Client documents may not be sent anywhere, so no step may depend on anything outside the folder itself.
- Nothing may be deleted, only moved
- Nine years of files include things whose importance is not obvious today. A rule that forbids deletion entirely removes the worst outcome before the work starts.
- Every original name stays recoverable
- The owner finds files by remembering what they were called, so a tidy name that loses the old one makes the folder harder to use, not easier.
- The owner is not technical
- If a step needs a command explained to the owner before it can be trusted, it will not be run a second time — so the plan has to be short enough to be understood once.
Five decisions that shaped the plan
A filing tidy-up can be done in many ways, and most arguments about it are really arguments about these five forks. Deciding them in writing, before anything moves, is what turns "sort my files" into something a second person could review.
Decision, then why
In plain words
- Sort by what a file is for, not by date
- Dates are already inside the files, so a date folder adds no information. Purpose — contract, draft, invoice — is the thing the owner actually searches by, and it is not recoverable from the file itself.
- Copy first, then move
- The rehearsal happens on copies in a separate folder. Only after the copies look right does the same set of instructions run against the originals, so a wrong rule costs a copy rather than a document.
- The old name is kept inside the new one
- Every moved file keeps its original name as the end of its new name, so a search for the old text still finds it and nothing has to be remembered.
- A written log of every move
- One line per file, in the order the moves happened, so the whole session can be read backwards if something turns out to be in the wrong place.
- One folder at a time, never the whole drive
- The instructions are given one folder to work in and told to stop when it is done. A plan that names its own boundary is one whose result can be checked in one sitting.
The permission plan is the plan
For work on pages, permissions are one section of four. Here they are the whole thing, because the interesting question is not what the tidy-up produces but what it is allowed to touch on the way. The table is written from a starting point of nothing: a row exists only because a step needs it.
| Location | May do | Must never do |
|---|---|---|
| The rehearsal folder | Read, create, move and rename anything inside it. This is the only place where a wrong rule is allowed to happen. | Reach outside itself, or read the original folder at all. |
| The original work folder | Read the file names and the dates already stored in the files. Later, and only after the rehearsal is signed off, move files into the agreed subfolders. | Delete anything, overwrite a file with a same-named one, or rename a file in a way that loses its original name. |
| Everything else on the computer | Nothing at all. Other folders are outside the task even when they look similar. | Be read, listed or searched, including the desktop and the downloads folder. |
| Anything outside this computer | Nothing. There is no step that needs a connection, so the whole task is done with networking irrelevant to it. | Receive a copy of any file, or any summary containing text from one. |
Comparison
The instructions, written out in full
The prompt below is the invented translator's, and it is written to be read by a person as much as by an assistant: the permission section is in it, the number of files it expects is in it, and so is the instruction to stop and report instead of carrying on. It contains no client names, no folder paths from a real machine and no document text.
The prompt, as it was pasted
Example
A filing tidy-up that never leaves one computer and never deletes anything. All names and counts are invented.
- Goal: put the files in my work folder into purpose-named subfolders, without losing a single file and without deleting anything.
- Where you may work: only the folder called "work", and only the rehearsal copy of it during the first pass. Do not read, list or search any other folder on this computer.
- The subfolders, and nothing else: Contracts, Drafts, Invoices, Reference. A file that clearly belongs to none of them goes into a folder called Unsorted rather than being guessed at.
- How to name a moved file: keep its existing name unchanged at the end of the new name, and put the year in front of it. Never shorten or translate a name.
- Never do any of these: delete a file, overwrite a file, rename a file without keeping its old name, move anything outside the folder, or open a file to read what is inside it.
- Stop and report instead of deciding: if the number of files is not between three thousand five hundred and four thousand five hundred, stop. If two files want the same new name, stop and list them. If anything looks like it does not belong in this folder, leave it in place and list it.
- What to give back: a list of every file with its old name, its new name and the subfolder it went to, plus a count of files before and after. I will compare those two counts myself.
The last two paragraphs are what make this an instruction rather than a wish. One says when to stop instead of choosing, and the other asks for exactly the evidence the owner needs in order to check the work without reading all four thousand names.
The rehearsal that came before anything moved
A rehearsal here means running the whole set of instructions on a copy, in a folder the owner does not depend on, with a small number of files chosen to include the awkward cases: two files with almost the same name, one whose date cannot be read, and one that plainly belongs somewhere else.
The log below is invented for this article, written the way such a log is written: one line per file, in the order the moves happened. It is here because the failures it contains are the ones that make the difference between "tidied my files" and "tidied my files and lost a contract".
The rehearsal log
Example
Twelve invented files, three of which did not go as the plan expected.
- Files at the start: 12. Files at the end: 12. Nothing was deleted, and the two counts matched.
- Ten files moved as expected, each keeping its original name at the end of the new one, each recorded on its own line with its old and new location.
- Failure 1: two files named almost the same thing both wanted the new name ending in the same text. The instructions say to stop and list them, and that is what happened — both were left where they were and written into the report.
- Failure 2: one file had no readable date, so no year could be put in front of it. It was moved into Unsorted with a note, which turns out to be the plan working rather than failing.
- Failure 3: one file was a photograph of a signed page. It has no purpose the plan can read, so it was left untouched and listed, but the plan never said whether an image counts as a document at all.
Two of the three failures were the plan working as written. Only the third was a genuine gap, and it was found on a copy for the price of one decision: whether a photograph of a page belongs in the same folders as the page.
| Finding | The missing line | The correction |
|---|---|---|
| Two files wanted one new name | Nothing was missing: the instructions already said to stop and list them. | No change. The rehearsal confirmed that a stop rule is followed, which is worth more than a rule that was never tested. |
| A file with no readable date | The naming rule assumed a year could always be found. | One added line: a file with no readable date goes to Unsorted with a note, and is never given an invented year. |
| A photograph of a signed page | The plan never said what counts as a document, so the instruction was silent about images. | One added line: an image whose purpose cannot be read from its name goes to Unsorted, and the owner decides it later. |
Comparison
How the owner checks the result without reading every name
The point of asking for a report is that it makes checking cheap. These seven steps take a few minutes on a folder of this size, and every one of them is something the owner does, not something the instructions ask to be believed.
Seven checks, in this order
- Compare the number of files before and after. If they differ by even one, stop and read the log before touching anything else.
- Search the whole folder for a few names you remember from before, and check that each one is found exactly once.
- Open one folder at a time and check that everything in it genuinely belongs together, rather than trusting the folder name.
- Look at the Unsorted folder first. It is the honest list of everything the instructions refused to decide, and it is where anything unexpected will be.
- Pick three files at random and open them, checking that the contents still match what the name promises.
- Check that the original folder no longer holds anything at the top level except the subfolders and the log.
- Keep the rehearsal copy and the log for at least a month. They are the only way back if something turns out to be misfiled after all.
When a filing plan fits, and when it does not
It fits when
- The work can be described as moves and renames, so that every action has a name and a recorded before-and-after.
- A copy can be made cheaply, so the first pass never touches the only version of anything.
- The owner is willing to read a short report, because an unread report is the same as no report at all.
- Nothing has to be thrown away yet, so the aim can be "everything is findable" rather than "everything is minimal".
It does not fit when
- The files are somebody else's, or are held under an agreement that says where they may be kept, because then the permission plan is not the owner's to write.
- The task depends on reading what is inside the documents — summarising, translating, extracting — because that is a different task with a different permission question, and it should be planned on its own.
- The folder is the only copy of anything important, and no copy is possible, because then the first step is a backup rather than an instruction.
- The owner cannot say what "tidier" means for their own folder, because a plan cannot supply a preference the owner has not formed.
Your next step
Three things to do with your own idea, in order. None of them needs an account, a tool or a Skill.
- Write down which folder the work may touch, and which it may never list or read.
- Make a copy, put a dozen awkward files in it, and run your instructions there before they touch anything real.
- Ask for a before-and-after count and a per-file list, and compare the two counts yourself.