Skip to main content

​
Prompting, explained simply

Prompting is how you tell Rocket what you want - clearly, in English.
It’s creative direction for AI. Rocket turns it into UIs, workflows, and fixes - fast.
What you’ll learn:
  • What prompting is and why it matters
  • Examples of effective prompts
  • Common mistakes to avoid

​
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. 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?

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.Quick examples:
  • /Update Content change "Welcome" to "Get Started" in hero section
  • /Add Element add testimonial card under features section
  • @pages/home.jsx update the CTA button text to match brand voice

​
Want to start immediately?

Copy one of these prompts and paste it into Rocket to see results quickly: 
Create a landing page with:
- Hero section: headline "Welcome to [Your App Name]", subheadline, and primary CTA 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.
Customize your app: After creating, use `/` commands like /Update App Name to change branding or /Change App Theme to apply your color scheme across all pages.Examples:
  • /Update App Name [Your App Name]
  • /Change App Theme primary color #4F46E5
  • /Fix Layout Issues for mobile breakpoints
Quick reference: 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

​
Common prompt mistakes to avoid

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

Mistake 1: Being vague

Don’t: Be vague.
Example: “Make a screen that shows some user data.”
Do: Be specific about what you want.
Try: “Create a dashboard that shows name, email, and last login date from the users table.”

Mistake 2: Asking for too much at once

Don’t: Ask for too much at once.
Example: “Create the UI, add logic, fix responsiveness, and make it look good.”
Do: Focus on one task at a time.
Try: “Build just the layout for now. I’ll add logic next.”
For more examples and fixes, see the Common mistakes and how to fix them section in Core concepts.