[← All Build It Videos](https://developers.google.com/profile/badges/builder/videos.md.txt) Episode 6 Google Antigravity E2E Testing System Spec

# Fix Your Vibe Coded App With One Prompt

When you fix UI bugs one prompt at a time without a system spec, each new fix can break existing components. In this episode, we step back from vibe debugging our Active Workout Tracker screen and define the page as a complete system inside our Design \& UX Spec: mapping components, page-level and exercise-level state variables (currentSet, restMode), conditional display rules, and button action mutations. Then we use Gemini to generate a comprehensive end-to-end test suite and pass both into Google Antigravity in a single prompt.
<iframe src="https://www.youtube.com/embed/ivW7cqypZEY" title="Fix Your Vibe Coded App With One Prompt" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen>
</iframe>

## Prompts and Artifacts

[Design \& UX Spec (Active Workout System) Artifact
Active Workout Tracker component mapping, state variables, display rules, and action mutations.](https://developers.google.com/profile/badges/builder/artifacts/design-ux-spec) [Implementation Plan \& Test Suite Artifact
Phase-gated execution roadmap and test suite verification gates.](https://developers.google.com/profile/badges/builder/artifacts/implementation-plan) [← Previous
Episode 5: Design Your App's Frontend Spec (No Code)](https://developers.google.com/profile/badges/builder/videos/video-5) [Next →
Episode 7: 6 Front-End Concepts Every AI Builder Needs to Know](https://developers.google.com/profile/badges/builder/videos/video-7)