This reminds me of Yeoman in a way. Never thought I’d reminisce about the days of backbone and gulp.
I will investigate it, but scaffolding to me is dangerous as it generates a lot of code that later cannot be as easily maintained/updated as it's been scaffolded. I look for a scaffolder/boilerplate that comes with updates when the base evolves!
Done properly and to the correct extent, scaffolding generates more maintainable code by ensuring that everything in all the codebases is structured in the same basic way, uses the same base libraries, has the same build steps, etc. Done over the top, it could include things most projects don’t need. Like anything, it requires using good judgment.
The idea here is not to dictate coding standards but rather to provide a tool that allows you to create your own scaffolds to use internally with your team. This helps simplify writing repetitive code and ensures that everyone is following the same coding standards.