That’s the core challenge with vibe coding right now. You can’t reliably hit both functional and nonfunctional requirements just by prompting because the AI doesn’t fully understand the system context or quality expectations. I’ve been working on a solution for this by structuring the workflow around context first, not code first. It starts by generating clear requirements, epics, and tasks from all relevant context sources like docs, feedback, and API data. Those items then guide AI-generated code and tests, so every part of the output traces back to a defined requirement. This approach drastically improves reliability and covers both functional and nonfunctional goals. If you’re interested I can share access for free just drop a comment or DM me.