Use this guide to avoid common pitfalls, speed up your workflow, and build high-quality apps with Rocket. It covers everything from prompting strategies and debugging to visual edits and deployment.

​
1. Treat prompts like instructions

Rocket is not a magic wand - it’s your AI engineer. The more clearly you explain what you want, the better it builds. When writing prompts:
  • Mention the page or screen (e.g., /pricing, /auth/login).
  • Describe what should happen.
  • Specify what not to change.
Good:
Create a pricing page, add three horizontally spaced plans, each with a name, price, feature list, and CTA.
Avoid:
Make a pricing page with cards.

​
2. Preview Before You Commit

Before implementing any changes, use the Preview panel to validate your build in a live-like environment. This helps catch layout bugs, logic errors, and role issues early before they go live. What to check:
  • Does the layout look and behave as expected?
  • Are all components loading the right data?
  • Are interactive elements (like buttons or forms) functioning correctly?
  • Are visibility rules (like role-based access) working properly?
  • How does it respond on mobile or small screens?

​
3. Fix smarter, not louder

When something breaks, don’t keep patching blindly. Fix it flow:
  1. Hit Fix it!
    or Describe the issue in chat.
  2. Review changes in preview.
  3. Roll back if needed.
Prompt example: 
The modal doesn’t close when clicking outside. Fix that without changing its structure.

​
4. Visual edit for quick tweaks

Use Visual Edit for:
  • Changing text, spacing, or order.
  • Fast layout fixes.
  • Undoable, token-free edits.
Fastest workflow: Prompt big changes → Visual tweak details → Preview → Repeat

​
5. Be Supabase-smart

Supabase is powerful but schema breakage is real. Best practices:
  • Connect it only after frontend is stable.
  • Don’t revert versions with live schema.
  • Test connected flows before publishing.

​
6. Own progress with version control

Don’t lose progress. Back it up. Options:
  • Download Zip anytime.
  • Sync to GitHub.
  • Use Code diff to track changes.

​
7. Rebuild if you’re stuck

Sometimes starting clean is faster than untangling bugs. When to rebuild:
  • After repeated failed fixes.
  • When the logic is deeply coupled.
  • When reverting causes schema issues.
Strategy: Keep the reference, and rebuild with focused prompts.

​
8. Don’t rush the last 10%

The app may be “done,” but polish matters. Final 10% checklist:
  • Empty states
  • Edge case feedback
  • Animations & transitions
  • Mobile responsiveness
  • Role-based visibility

​
9. Use docs, ask for help

If you’re stuck:
  • Browse guides and patterns.
  • Try related prompts.
  • Email us or join the community.
You’re not alone. Ask early, ship faster.

​
10. Bonus moves (Pro tips)

  • Custom domain? Use Netlify and add custom domain there.
  • Tokens low? Top-up mid-cycle without upgrading your plan.
  • Ownership? You own 100% of your code - Rocket doesn’t keep any rights.
  • Slow builds? Preview iteratively. Long prompts = longer generation times.
  • Multiple roles? Always define which role the prompt applies to.
Ready to build smarter? Prompt boldly. Preview often. Polish with purpose.
Need help? We’re here for you.
Email us at support@rocket.new or join our Discord community to get help, share ideas, and connect with other creators.