Skip to main content

​
Prompting, explained simply

Prompting is how you tell Rocket what you want - clearly, quickly, and in plain English.
It’s not code. It’s not config. It’s creative direction for AI, and Rocket turns it into results: UIs, workflows, fixes - fast.
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. Prompting well is a skill - but an easy one to pick up.

​
What happens when you prompt Rocket?

Rocket interprets your prompt across three layers:
  1. Intent – What are you trying to achieve?
  2. Structure – What UI, data, or logic elements are involved?
  3. Output – What should Rocket generate, and how?

​
Prompt Examples:

Create a welcome screen with a short headline, one sentence of text, and a big button that says "Get started".

When someone books a session, save their name and time, show a thank-you message, and send a calendar invite.

The “Next” button isn’t working on the sign-up screen. Make sure it’s visible, clickable, and linked to the next step.

​
Prompting is not guessing

Clear prompts = better results. Here’s what works:
  • Specific - Say exactly what you want.
  • Simple - Tackle one idea at a time.
  • Descriptive - Add meaningful details: layout, behavior, content, etc.
If you can explain it to a teammate or write a great search query, you already know how to prompt.

​
Prompting is like…

  • Writing a scene, not a script.
  • Giving instructions to a fast, capable teammate.
  • Describing your idea out loud - Rocket builds the rest.
Start with:
“What should this app, screen, or feature do?”
Then describe it in one clear sentence.

​
Why prompting is powerful

  • Uses natural language. No special syntax - just clear English.
  • Delivers instant results. Build and iterate in seconds.
  • Enables fast debugging. Describe a problem, and Rocket helps resolve it.
  • Improves with use. The clearer your intent, the better Rocket performs.

​
Common prompt mistakes to avoid

Even if your idea is clear in your head, Rocket only sees what you type. Here’s how to avoid common pitfalls:
Don’t: Be vague.
Example: “Make a screen that shows some user data.”
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 too many actions.
Example: “Create the UI, add logic, fix responsiveness, and make it look good.”
Do: Focus on one task.
Try: “Build just the layout for now. I’ll add logic next.”
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.”
Prompting gets better with practice. Your next guide shows how to apply these strategies with intent.