Fix App That Looks Good But Does Not Work
Debugging
60-120 minutes0/6 steps0%
Step 1 of 6
Run a brutal functional audit
Get the honest map: what works, what is fake, what is broken.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Prompt Capsule
Audit this app feature by feature with zero optimism. For every feature/screen: perform its primary action for real, then refresh and check persistence. Classify each as WORKS (action real + persists), FAKE (UI responds but nothing real happens), or BROKEN (errors/dead). Produce the table: feature -> action tested -> observed result -> classification. Do not skip auth, forms, filters, or buttons in modals.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements
Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.
Actual change check
Expected after this step
A complete truthful WORKS/FAKE/BROKEN feature table.
Should NOT happen
- An existing feature broke
- A button only logs to console
- Data disappears after refresh
- Errors fail silently with no visible state
This is what should exist before you continue. If reality does not match, do not move on.
Track what changed, failed, or needs follow-up. Notes export with the flow.
Pass the Verify Gate to complete this step