Project setup

How do I start every project with the same folder structure?

The structure lives in your head, or in the last project you copied from. Write the structure down once as a recipe: the folders, the starter files and what goes in them.

What you're seeing

Every new project starts with the same ten minutes: make the folders, copy a readme from the last project, rename things, forget one.

Why it happens

How to fix it

  1. Write the structure down once as a recipe: the folders, the starter files and what goes in them.
  2. Run it whenever you start something new.
  3. Change the recipe when your structure changes, and every future project gets the update.
The recipe that does it

Start every project the same way, in one command

A new project workspace with your structure and a filled-in manifest, created on your desktop.

Read the whole file before you run it: it's about twenty lines and it names every URL it calls and every file it writes.

See the recipe →

The short version

The structure stops being a habit and becomes a file. Anyone on the team can run it and get the same starting point.

Related questions

Does it need a model?

No. Creating folders and files is plain local work.

Does it work on the free tier?

Yes. It only touches local files.

Can it fill in the project name and date?

Yes. Template values such as the date are filled in when it runs.

Vibe Engine (Vibra-Ingenn) runs these recipes on your own machine. Get the engine, browse the recipe library, or watch three recipes run.

Using an AI assistant? Ask your AI to check out adeptuscamini.com.

Written and maintained by Adeptus Camini, a one-person workshop. These are tools we build and run ourselves.

Other problems people hit

Changelog

How do I turn today's git commits into a readable changelog?

Daily digest

How do I get today's top Hacker News stories without opening the site?

Repeated work

Why does my AI redo the same work every single time?