​
Prompting, explained simply

Prompting is how you tell Rocket what you want - clearly, quickly, and in plain English.
It is not code. It is not configuration. It is a fast, intuitive way to describe your app idea or action and have Rocket build it for you.

You describe your intended outcome. Rocket generates the UI, logic, workflows, or fixes right away.

Prompting is creative direction for AI. You describe the result. Rocket figures out the how.

​
Why prompting matters

Prompting is the foundation of everything you do in Rocket. With just a few words, you can:

  • Create an app from scratch.
  • Edit or expand existing screens.
  • Automate logic and workflows.
  • Debug issues and fix behavior.
  • Move seamlessly between design and implementation.

The clearer your prompt, the more precise your output.

​
What happens when you prompt Rocket?

When you submit a prompt, Rocket interprets it in three layers:

  1. Intent – What you are trying to accomplish.
  2. Structure – What elements (UI, data, logic) are needed.
  3. Output – What to generate and how to present it.

Here’s what that looks like in practice:

Create a dashboard with 3 widgets: sales summary, conversion chart, and active users.

When someone submits a form, send their data to database and email them a confirmation.

Why isn’t the "Next" button working on my onboarding screen?

​
Prompting is not guessing

While prompting feels natural, the best results come from clarity. A strong prompt is:

  • Specific. State the exact outcome you want.
  • Simple. Focus on one task or idea at a time.
  • Descriptive. Include the details that matter, such as layout, behavior, or inputs.

If you can explain an idea to a teammate or phrase a great search query, you already know how to prompt.

​
Prompting is like…

  • Writing a scene, not a script.
  • Giving clear instructions to a capable builder.
  • Describing your idea out loud - Rocket handles the implementation.

Start with:
“What should this app, screen, or feature do?”
Then describe it in one clear sentence.

​
Why prompting is powerful

  • Uses natural language. You don’t need special syntax or terminology.
  • Delivers instant results. Build and iterate in seconds.
  • Enables fast debugging. Ask a question or describe an issue to resolve it.
  • Improves with use. The more intentional your prompts, the better the results.

​
Common prompt mistakes to avoid

Even if your idea is clear in your head, Rocket only sees what you type. These are a few early mistakes we see often and easy ways to avoid them.

Don’t: Be vague.
Example: “Make a screen that shows some user data.”

Rocket might guess what you mean, or generate the wrong kind of output.

Do: Be specific.
Try: “Create a dashboard that shows name, email, and last login date from the users table.”

Don’t: Overload your prompt with multiple tasks at once.
Example: “Create the UI, add logic, fix responsiveness, and make it look good.”

Do: Focus on one goal at a time.
Try: “Start by building just the layout. I’ll add logic in the next step.”

Don’t: Assume Rocket knows your preferences.
Example: “Make it user-friendly and fast.”

Do: Define what that means.
Try: “Use large input fields, minimal text, and a single-step submission flow.”

These are just a few early mistakes to watch for.
The next guides will show you how to write better prompts.