Brainstorming: Looking further than validation: creating configs

Hey people,
Something has been stirring my mind for a while: validating existing configs is nice, but the problem starts earlier: the point when you start building your config. It's just overwhelming. Copy pasting from existing, complex configs is suboptimal, you don't understand the stuff you're doing. And creating it from scratch is difficult too: you alt tab between webpack configuration documentation and your editor, rinse and repeat; probably followed by many hours of searching miscellaneous GitHub issues for best practices.
I wonder how this could be optimized. I don't want another abstraction over webpack, users should stay in control when needing advanced customization. I imagine some form of interactive guidance, incorporating and hinting at best practices from the beginning. One approach would be a web service like webpackbin does it, providing inline hints etc. back and forth copy pasting to usage in local project is suboptimal though. Yeoman generator would be another option, I'd like something that's more incremental though. Maybe some interactive cli thing that analyses existing webpack config and provides hints and suggests additions and modifications over time. Like an experienced pair programmer who has all webpack config and existing best practices in his head all the time. :)

So, just some rambling thoughts here. I'm just interested in your thoughts on something like that.

No file, test, or entry point is named. Start by reviewing the repository's existing webpack-config validation flow and Joi-based behavior, then define a concrete interactive guidance scope and acceptance criteria before implementation. Done requires an agreed design and explicit behavior to validate.