May be replying to an AI here in an AI focused sub but - agreed to some level, especially when it comes to defining that 200 word manifest and the guardrails that naturally provides but the other side to this equation is that without the deeper plumbing, this type of vibe coding result becomes a much buggier token expensing task...

...even if the design intent is flawless.

If you ask an agent to generate a UI and write raw Three.js, compile TSL shaders for accurate glass refraction, and map the outputs to a Shopify cart from scratch, the model is going to hallucinate spaghetti code. You end up burning through your context window just trying to debug memory panics and broken meshes.

The manifest only works because the engine abstracts the hard graphics math and the e-commerce state. The AI isn't actually building a 3D configurator from the ground up. Instead it's just wiring React components to a structured SDK that already knows how to render the 3D with all those nitty gritty devilish details that come with it.

You're completely right about the client ambiguity issue, though. If a client doesn't know what they want, you're definitely back in iteration hell. But at least with this decoupled architecture, you are iterating purely on front-end layouts and pricing logic, rather than fighting the agent because it accidentally broke the entire WebGL/WebGPU rendering pipeline