Skip to main content
This guide helps you get more out of Rocket. You’ll learn how to structure prompts, fix issues quickly, make visual tweaks, and deploy with confidence.

​
1. Be clear with prompts.

Rocket builds what you ask. The clearer your instructions, the better the result. What to include:
  • The exact page or screen name (e.g. /pricing, /auth/login).
  • What should appear or happen.
  • What should stay untouched.
Good Prompt Example:
Create a pricing page with three horizontally spaced plans. Each should have a name, price, feature list, and call-to-action.
Avoid Prompts like:
Make a pricing page with cards.

​
2. Always preview first.

Before applying changes, use the Preview panel. It shows your app in a live-like view and helps catch issues early. Preview checklist:
  • Layout and responsiveness.
  • Data loading and logic.
  • Button clicks and form actions.
  • Role-based access.
  • Mobile behavior.

​
3. Fix issues the smart way.

When something breaks, avoid guesswork. Use Rocket’s built-in tools to resolve issues confidently. Do this:
  1. Click Fix it!, or
  2. Describe the problem in chat.
  3. Preview the fix.
  4. Roll back if needed.
Example prompt:
The modal doesn’t close when clicking outside. Fix that, but keep the structure the same.

​
4. Tweak with visual edit.

Use Visual Edit to adjust layout, spacing, text, and element order. These changes are safe, fast, and token-free. Great for:
  • Small copy changes.
  • Reordering blocks.
  • Fast design tweaks.
Speed tip: Use prompts for structure, then fine-tune visually.

​
5. Connect Supabase carefully.

Supabase is powerful, but schema changes can break things if not managed properly. Play it safe:
  • Connect Supabase only after the layout is stable.
  • Avoid reverting versions with a live schema.
  • Test connected flows before publishing.

​
6. Use version control.

Back up your app regularly. It only takes a few clicks to stay safe. Ways to back up:
  • Download your app as a ZIP file.
  • Sync with GitHub.
  • Use Code Diff to track what changed.

​
7. Know when to rebuild.

Sometimes it’s faster to start fresh than untangle a complex build. Rebuild when:
  • Fixes keep failing.
  • Logic is deeply nested or messy.
  • Reverts cause schema errors.
Rebuild tip: Save a screenshot or prompt, then rebuild with focus.

​
8. Polish the final 10%.

Your app might work, but small refinements matter. Final 10% checklist:
  • Empty and error states.
  • Animations and transitions.
  • Role-based visibility rules.
  • Small screen layouts.
  • Edge case handling.

​
9. Use the docs. Ask for help.

If you’re stuck, don’t wait. There’s always a next step. What to do:
  • Browse the guides.
  • Try a related prompt variation.
  • Reach out or ask in the community.
You’re not alone. Ask early. Ship faster.

​
10. Bonus moves (Pro tips).

  • Custom domain? Use Netlify to connect your domain.
  • Low on tokens? Top up mid-cycle without changing plans.
  • Code ownership? You own 100%. Rocket doesn’t claim rights.
  • Slow generation? Use shorter prompts or preview in smaller steps.
  • Multiple roles? Always mention which role the prompt applies to.
Build smart. Launch fast.
Prompt clearly. Preview constantly. Polish with care.
Need help?
Email us at support@rocket.new or join our Discord community to get help, share ideas, and connect with other creators.
⌘I