@kytta Theoretically I would use `./scripts` for development tools and `./bin` for other maintenance tools. Deploy tools might fall in either category depending on the type of project.

In practice I often start out by just having one of those and dump everything there. In that case it might be a bit random if it ends up being named `./bin` or `./scripts`.

I would put them into the root directory. For additional things that one would run manually, e.g. code generation or validation, I use ./tools.

./build in my mind is where intermediate build artifacts go because that's what Android Studio does.

@kytta I prefer putting this kind of stuff in a Makefile 🤷‍♂️
These actions are often interconnected, e.g. package requires build, build requires fetch_deps, etc. Makefile makes it trivial to manage and good for discoverability.

But if not, then I'd go with ./bin probably.

@kytta I use “just” instead to build them. Sort of like Makefiles but better.