This is very similar to a project I attempted to create called Ember Boilerplate (never released), which was a play on Backbone Boilerplate (<a href="https://github.com/tbranyen/backbone-boilerplate" rel="nofollow">https://github.com/tbranyen/backbone-boilerplate</a>) and (<a href="https://github.com/backbone-boilerplate/grunt-bbb" rel="nofollow">https://github.com/backbone-boilerplate/grunt-bbb</a>). Mine failed to be released, because I don't think I addressed the concerns and needs of Ember developers.<p>Very glad someone who is entrenched in the Ember community could provide the same necessities and insight to the same problems I was able to fix for Backbone developers. Tools like Brunch and Yeoman attempt to accomodate all libraries, which is an admirable goal, but I feel like developers who write applications in a specific framework every day are more keen on providing necessary defaults.<p>Perhaps soon we'll have some agreed upon common ground: (CommonJS modules, template pre-compilation, image optimizations, source maps, etc.) and leave the scaffolding and defaults to specific projects that address the needs and desires for developers using those frameworks.