Debug without guessing

Explain an error message

Turn a confusing error into a useful next step.

Use it when
When you want to understand a failure before fixing it.

Before moving on
Ask for missing error text and avoid recommending destructive reset commands.

Fix a console error

Resolve the error behind a visible problem.

Use it when
When the browser console shows a repeatable error.

Before moving on
Reproduce the original flow and check for new related errors.

Fix a button that does nothing

Restore a broken action without redesigning the page.

Use it when
When a click produces no useful result.

Before moving on
Check success, failure, loading state, and existing surrounding behavior.

Fix a hydration mismatch

Align the server-rendered page with the browser render.

Use it when
When a supported framework reports a hydration error.

Before moving on
Check initial load and navigation; do not merely suppress the warning.

Fix refresh on a nested route

Make direct visits behave like in-app navigation.

Use it when
When refreshing a deeper page returns a 404.

Before moving on
Check direct load, refresh, client navigation, and real unknown-route 404 behavior.

Review the latest changes

Understand what the AI edited before accepting it.

Use it when
When you want a plain-English review of your working changes.

Before moving on
Reference affected files and separate confirmed problems from possibilities.