Skip to main content
Prompting is how you tell Rocket what you want, clearly, in plain English. You describe the goal and Rocket turns it into UIs, workflows, and fixes.The clearer your prompt, the more precise the output.This page covers:
  • What prompting is and how Rocket interprets it
  • Examples of effective prompts
  • Common mistakes to avoid

​
Why prompting matters

Prompting is the foundation of everything you do in Rocket. With 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 between design and implementation
The S.I.M.P.L.E. checklist from Core concepts helps you write prompts that are specific, focused, and easy to debug.

​
What happens when you prompt

Rocket interprets your prompt across three layers:

Intent

What are you trying to achieve?

Structure

What UI, data, or logic elements are involved?

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".
Start with: “What should this app, screen, or feature do?” Then describe it in one clear sentence.
After creating, use / commands like /Add Element to insert components or /Update Content to change text. For edits scoped to specific files, use @ commands.

​
Try it now

Copy one of these prompts and paste it into Rocket to see results: 
Create a landing page with:
- Hero section: headline "Welcome to [Your App Name]", subheadline, and primary CTA (Call To Action) button "Get Started"
- Features section: 3 feature cards in a row with icons, titles, and descriptions
- Final CTA section before footer
Use a clean, modern design with plenty of white space.
After creating, use /Update App Name to change branding or /Change App Theme to apply your color scheme across all pages.

​
Common prompt mistakes

Even if your idea is clear in your head, Rocket only sees what you type. Here are two patterns to avoid:

​
Being vague

Do not do this: “Make a screen that shows some user data.”
Instead, be specific: 
Create a dashboard that shows name, email, and last login date from the `users` table.

​
Asking for too much at once

Do not do this: “Create the UI, add logic, fix responsiveness, and make it look good.”
Instead, focus on one task at a time: 
Build just the layout for now. I will add logic next.
Three key principles for effective prompting:
  1. Be specific - Say exactly what you want, not just how it should “feel”
  2. Stay focused - Tackle one idea at a time. Break complex tasks into smaller prompts
  3. Add context - Include meaningful details: layout, behavior, data sources, interactions
For more examples and patterns, see Core concepts.Need ready-to-use prompts? Browse the Prompt library. Running into issues? Check the Debugging guide.