Debugging

When something in your app is not working as expected, debugging means figuring out what is wrong and fixing it. In Rocket, you do this by explaining the problem clearly so the AI can help you fix it without starting over.This guide covers:

How to describe problems so they are easy to fix
Quick commands for common issues
How to make small, safe fixes instead of big rewrites
Common integration errors and fix prompts

When something goes wrong

Before you write a long message, try these quick checks:

Refresh the page

Sometimes the page just needs to reload.

Undo your last change

If you know what broke it, undo it.

Check for typos

Look for spelling mistakes in names and labels.

Check your settings

Make sure your connections and configuration are correct.

Try simple commands before writing a long debugging message:

/Fix Navigation Issues for broken links or pages not loading
/Fix Layout Issues for spacing, alignment, or things looking wrong
/Fix Theme Switching for problems switching between light and dark mode

How to describe problems

The best way to get help is to explain your problem clearly. Use this template:

1. What I expected:
   [Describe what should happen]

2. What actually happened:
   [Describe what happens instead]

3. Error message (if any):
   [Copy any error messages you see, or say "no error message"]

4. Where this is happening:
   [Which page or part of your app]

5. What I already tried:
   [List anything you already checked or changed]

Then ask Rocket to help:

Based on this information, explain what is most likely causing this issue.
Then suggest a safe, minimal change to fix it.

Example

1. What I expected:
   On the login page, when I enter my login information and click submit,
   I should go to the main dashboard page.

2. What actually happened:
   I click submit, the button shows it is working for a moment,
   but then I stay on the login page. The page address does not change.

3. Error message (if any):
   I see an error message that says: "Cannot read property 'userId' of undefined"

4. Where this is happening:
   The login page

5. What I already tried:
   - Checked that my login information is correct
   - Made sure the information is being saved
   - Tried opening in a different browser

Step-by-step guide when something breaks

Check for error messages

Look for any error messages on the screen or in the browser.

If you see an error message, copy the exact text and use it in your problem description.
If you do not see an error message, move to the next step.

Check if something looks wrong

Compare what is on the page to what you expected.

If something looks wrong, describe what you expected and what you actually see.
If everything looks correct, move to the next step.

Check if nothing happens

If clicking buttons or interacting with the page does nothing at all:

Look more carefully for error messages you might have missed
Describe what should happen when you interact with the page
Describe what actually happens (nothing)

Write your message

Use the template from “How to describe problems” above to organize what you found. Include the error message, what looks wrong, or what does not respond.

Quick commands for common problems

Rocket has special commands that can fix common problems quickly. Try these before writing a longer message.

Layout and spacing

/Fix Layout Issues fixes things that look misaligned or spaced wrong
/Fix Layout Issues in pricing grid fixes layout in a specific area
/Fix Layout Issues for mobile breakpoints fixes responsive layout issues

/Fix Navigation Issues fixes broken links or pages that do not load
/Fix Navigation Issues in header navigation targets a specific area
/Fix Navigation Issues for dashboard routes targets specific routes

Theme

/Fix Theme Switching fixes problems switching between light and dark mode

/Fix Supabase Authentication Issues fixes common login and signup problems
/Fix Supabase Authentication Issues for users who can sign up but cannot log in targets a specific scenario

Code organization

/Organize Code cleans up messy or hard-to-find code
/Organize Code in src/components/dashboard.tsx targets a specific file

Scoping changes to one file

Use @ followed by the file name to make sure changes only happen in that file:

@pages/login.jsx fix the submit button behavior

Common problems and how to fix them

Only fix one specific thing

The popup window opens correctly, but closing it does not work:
- Clicking outside the popup does nothing
- The "Cancel" button sometimes works, sometimes does not

Only fix how the popup closes:
- Clicking the area behind the popup should close it
- The "Cancel" button should always close it
- Pressing the Escape key should close it

Do not change how it looks or any other parts of the page.

Ask for an explanation first

This list is showing the same items twice, and sometimes
it does not update when I add a new item.

First, explain in simple terms what might be causing:
- Why items appear twice
- Why new items do not show up

Then suggest a small change to fix both problems,
and only make that change.

Something feels slow

Try /Fix Layout Issues first. Sometimes layout problems make pages feel slow. If that does not help:

This page feels slow when loading a lot of information.

Check for things that might be making it slow:
- The page refreshing when it does not need to
- Loading the same information more than once
- Loading too much information when the page first opens

Explain what is making it slow, then suggest specific ways to make it faster.
Do not change how it looks, just focus on making it work better.

Button does not work

Use @pages/profile.jsx to limit changes to one file, then describe the problem:

@pages/profile.jsx fix the submit button behavior. Check what happens when clicked and when form is submitted.

On the "Save" button in the profile form, clicking it does nothing:
- The button is visible and I can click it
- Nothing happens when I click
- No error message appears
- The information does not save

Do not change how the form looks or how it is styled.

Information does not save

Use @pages/tasks.jsx to limit changes to one file:

@pages/tasks.jsx check whether the save function is being called and whether data is being sent correctly.

When I update a task and click "Save", the changes show up temporarily
but disappear after I refresh the page. The information is not being saved
to where it is stored.

Check:
- Whether the save function is being called
- Whether the information is being sent to where it is stored correctly
- Whether the response is being handled properly

Focus only on making sure information saves. Do not change how it looks.

Something does not show up

Use @pages/dashboard.jsx to limit changes to one file:

@pages/dashboard.jsx check whether the user list is set up correctly and whether data is being loaded properly.

The user list does not show up on the dashboard page.
The page loads, but the list area is empty even though there are users
stored in the system.

Check:
- Whether the list is set up and used correctly
- Whether the information is being loaded properly
- Whether there are any errors preventing it from showing

Do not change other parts of the dashboard.

Here is how a vague message becomes a clear one. Bad (too vague):

The login is broken, please fix.

Does not say which page, does not explain what should happen, no error message or details.

Better (still needs work):

Login does not work after the user signs in.

Good (clear and actionable): First try /Fix Supabase Authentication Issues. If that does not work, use a detailed description:

1. What I expected:
   On the login page, when I enter my login information and click submit,
   I should go to the dashboard page.

2. What actually happened:
   I click submit, the button shows it is working for a moment,
   then I stay on the login page. The page address does not change.

3. Error message:
   I see an error message that says: "Cannot read property 'userId' of undefined"

4. Where this is happening:
   The login page

5. What I already tried:
   - Checked that my login information is correct
   - Made sure the information is being saved
   - Tried opening in a different browser
   - Tried /Fix Supabase Authentication Issues

Then follow up:

@pages/login.jsx based on this information, identify the most likely cause of the issue
and propose a small, focused fix. Explain the change before applying it.

What to avoid

Being too vague

Do not do this: “The form is broken.”

Instead:

On the "Contact" form, clicking "Submit" does nothing:
- Nothing happens when I click
- No success or error message appears
- No information is being sent

Help me fix only the submit button behavior.

Or even better: @pages/contact.jsx fix the submit button behavior. Nothing happens when clicked, no error appears, and no data is sent.

Asking for too much at once

Do not do this: “Fix the checkout process.”

Instead:

On the checkout page, the payment button shows it is working but never finishes.
The form checks work correctly. Focus only on making the payment button work.

Or: @pages/checkout.jsx fix the payment button so it completes properly. The form validation works correctly.

Not giving enough details

Do not do this: “The table is not showing information.”

Instead:

The "Orders" table is empty even though there are orders stored in the system.
The table layout looks correct, but no rows appear. Check how information
is loaded for this table.

Saying “sometimes it does not work”

Do not do this: “Filtering does not always work.”

Instead:

On the "Orders" table, filtering by status works for
"Pending" and "Completed", but selecting "Cancelled"
shows an empty table even though there are cancelled orders
stored in the system.

Focus on making filtering work for the "Cancelled" status.
Do not change how the table looks or how it is styled.

When your messages are not working

If you have used the template above but Rocket keeps making changes that do not help:

Situation	What to try
Fix is completely wrong	Be more specific about the problem. Use the template structure.
Fix is partially right	Add more details about the problem. Include error messages and location.
Changed the wrong parts	Clearly state what NOT to change. Use `@` to scope to one file.
Fix changes each time	Break the problem into smaller parts. Fix one issue at a time.
Ignores your existing work	Point to similar parts that work correctly. Show what you want it to look like.

If you are stuck, try explaining the problem to someone else in plain English. The words you use to explain it are often the words you should use in your message to Rocket.

Common integration errors

The most frequent integration errors for Supabase, Stripe, email, AI, and deployment are documented with causes and fix prompts in the Troubleshooting page. If you are hitting an error from a connected service, check there for step-by-step solutions.

What’s next?

Troubleshooting

Step-by-step fixes for common integration and deployment errors.

Best practices

Prompt patterns and iteration strategies for complex apps.

Prompt starters

Ready-made prompts for common design and UI tasks.

FAQ

Answers to the most frequently asked questions.

LEARN

TUTORIALS

PROMPT STARTERS

TEMPLATES

WORKFLOWS

RECIPES

GUIDES

EXAMPLES & VIDEOS

When something goes wrong

How to describe problems

Example

Step-by-step guide when something breaks

Quick commands for common problems

Layout and spacing

Navigation

Theme

Code organization

Scoping changes to one file

Common problems and how to fix them

What to avoid

Being too vague

Asking for too much at once

Not giving enough details

Saying “sometimes it does not work”

When your messages are not working

Common integration errors

What’s next?

Troubleshooting

Best practices

Prompt starters

FAQ

​When something goes wrong

​How to describe problems

​Example

​Step-by-step guide when something breaks

​Quick commands for common problems

​Layout and spacing

​Navigation

​Theme

​Login and authentication

​Code organization

​Scoping changes to one file

​Common problems and how to fix them

​Example: Fixing a login problem

​What to avoid

​Being too vague

​Asking for too much at once

​Not giving enough details

​Saying “sometimes it does not work”

​When your messages are not working

​Common integration errors

​What’s next?

Troubleshooting

Best practices

Prompt starters

FAQ

When something goes wrong

How to describe problems

Example

Step-by-step guide when something breaks

Quick commands for common problems

Layout and spacing

Navigation

Theme

Login and authentication

Code organization

Scoping changes to one file

Common problems and how to fix them

Example: Fixing a login problem

What to avoid

Being too vague

Asking for too much at once

Not giving enough details

Saying “sometimes it does not work”

When your messages are not working

Common integration errors

What’s next?