Thinking of building services around the Vibe Coding workflow. What do guys think actually want?

We’ve been exploring how parts of the vibe coding workflow could evolve into a set of services, not as a product pitch, but as a way to understand what the community actually needs.

For those building in the vibe‑coding style day to day:
Which parts of your workflow still feel clunky, unguided, or too manual?
Is it the setup process, debugging, architectural planning, or the creative exploration side?

Our goal is to find a direction that genuinely supports the ecosystem instead of adding yet another generic layer that slows things down.

Bottom line: we’re not building another IDE. We’re focused on bridging the gap between creator and tool — making those connections, like MCP and similar integrations, feel seamless and natural.