The @project scripts setup the whole environment, alias the appropriate build tools and versions of …

… The @project scripts setup the whole environment, alias the appropriate build tools and versions of those tools, prepare the correct IDE config if needed, drop me in the project's directory, etc. Some start a VPN connection because some of my clients only have git access over VPN etc. Because I've worked on many things over many years, most of these scripts also output some "help" output so I can remember how shit works for a given project. Here's an example: # @foo PROJECT FOO ----------- VPN Connection: active, split tunnel Commands: tests: mvn clean verify -P local_tests build all components: buildall Tools: java version: 17.0.16-tem maven version: 3.9.11 Edit: a word on aliases, I frequently alias tools like maven or ansible to include config files that are specific to that project. That way I can have a .m2 folder for every project that doesn't get polluted by other projects, I don't have to remember to tell ansible which inventory file to use, etc. I'm lazy and my memory is for shit.