Skip to content
Flows
Fix Broken Buttons
Debugging30-60 minutes
0/5 steps0%

Step 1 of 5

Inventory every interactive control

You cannot fix what you have not listed - audit first.

Prompt capsule

Audit this entire app and produce a table of EVERY button, link, icon-button, and menu item: its label/location, what it is supposed to do, and its current status (WORKS / DEAD / FAKE - fake meaning it shows feedback without doing the real action). Actually inspect the handlers; do not guess. Include modals, dropdown items, and mobile-only controls.

Paste into Claude · Complete implementation prompt with explicit requirements

Expected after this step

A complete control inventory with WORKS/DEAD/FAKE status per item.

Should not happen

  • Buttons with no onClick handler at all
  • Handlers that only console.log
  • Success toasts with no underlying action
  • Buttons that work once then break due to state bugs

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Do not continue if…

  • !Buttons with no onClick handler at all
  • !Handlers that only console.log
  • !Success toasts with no underlying action
  • !Buttons that work once then break due to state bugs

If the AI messes this up

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The inventory missed controls or guessed statuses. Re-scan every route and component file for clickable elements and verify each handler's real behavior.

Your notes for this step