glad that it helped @noahdecoco, I started my most recent project without a skeleton, but definitely did use one for the first few projects. What I would need to do to walk you through that is expand on step 6 and 7, because you need to setup your project folder structure where Brunch will watch and where it will output and you need to setup your config.coffee (or config.js) which is where you include all of those commands and instructions that identify the path to watch and the order to compile files etc. This is where the Brunch documentation https://github.com/brunch/brunch/blob/stable/docs/config.md comes in. Packages for NPM and Bower will configure themselves if you run npm init and bower init and then use npm install and bower install to actually pull in the dependencies. That's the beauty of those package managers, you never have to touch the config files if all the packages you are using are properly configured which 80-90% will be. Just make sure you use the --save or -S flags accordingly when running the install commands or it won't add it to the packages.json, it will just pull the files.