A folder convention erodes. It survives three calm weeks and then a rushed deadline puts a project in the wrong place with the wrong name, and a year later nobody can find anything.
fastf is the fix that treats the convention as code. You describe the structure once as a template: the naming pattern, the subfolders, the starter files and what should be filled into them. From then on, creating a project means answering a few questions and getting a result that is always consistent, always numbered, and always findable months later.
The same tool for very different people
The templates are the product, so the tool is not specific to software.
- A video editor gets a delivery ready episode folder for every video.
- A designer gets brief and asset folders named for the client.
- A journalist gets a story folder with places for interviews, footage, and drafts.
- A developer gets a code scaffold with configs ready to build.
Two surfaces, one engine
Running fastf with no arguments opens a guided terminal menu with a live preview of the folder tree, a library browser with folder sizes filling in as they are measured, and a mover with a progress bar you can cancel. Escape always goes back, and a rejected answer comes back editable rather than lost.
Nothing is menu only. Every action has a scriptable equivalent, so the same tool works inside a shell script.
Small on purpose
The whole thing is one self contained Rust binary under four megabytes with no runtime dependencies. It has no network surface at all: it reads and writes files on the machine it runs on and does nothing else. Install it from a package manager or carry it on a USB stick.
It is a single user tool for self contained project trees. Coordinating simultaneous writers across machines is a different problem and a different program.