This is a refreshing take on the vibe coding trend. What struck me most is your point about the context gap—AI generates individual functions well but struggles to connect them efficiently. I think this hints at a deeper shift: the skill isn't just prompt engineering, it's context engineering.
The CopilotKit example perfectly illustrates this. When the Agent didn't know to check the docs, it tried to reinvent UI components. The fix wasn't a better prompt—it was providing the right context (the documentation). As these tools evolve, I suspect the winners won't be those who write the cleverest prompts, but those who know what context to surface and when.
The security concern you raised is underappreciated. As vibe coding moves from prototypes to production, the question shifts from "can AI build it?" to "should AI see this code?" Enterprise teams will need clear boundaries around what prompts go to external models versus what stays local.
Great article—this captures where we actually are, not where the hype says we are.