You're contradicting the problem that you've set out to solve. Now at a hackathon, when debating with my team which frameworks to use etc we now have another scaffolding tool to debate over. This involves those who might not like yeoman, may not prefer the template library you're giving them. As well there will be those who've looked at your repo and simply don't agree with the code your scaffolding.
I like the idea, I really do, but the problem you're solving is all wrong. This isn't a solution for teams to get organized, because in the end you're just another member of their team saying "This is whats best".
This is a solution for a team who finds themselves at a real-time/node/web-app hackathon working with technologies they don't know and its a quick way to guide them in "A" direction, weather its the right or not they will decide once they learn more.
I like the idea, I really do, but the problem you're solving is all wrong. This isn't a solution for teams to get organized, because in the end you're just another member of their team saying "This is whats best".
This is a solution for a team who finds themselves at a real-time/node/web-app hackathon working with technologies they don't know and its a quick way to guide them in "A" direction, weather its the right or not they will decide once they learn more.