Skip to main content
Precise control from chat.Commands let you make targeted edits without describing everything from scratch. Use / for screen-aware shortcuts and @ for file-scoped changes.
Commands are only available on the web browser. They are not supported in the Rocket mobile app.

How commands work

Both commands run from the chat input. Type / or @ to get started.
/ commands@ commands
What they doScreen-aware shortcuts that update the page you have openTarget a specific file or folder to keep edits scoped
How to triggerType / in chat and browse the popup menu, or start typing to filterType @ in chat and pick a file or folder from the picker
TargetingRuns on the current open screen automaticallyLocks scope to your selected file or folder
Best forQuick updates, layout fixes, content changes, integrationsPrecise edits to known files, isolated component changes
After either command runs, you’ll see a short summary and a preview link to review changes.
Save tokens: One specific / command beats a long description. Quoting exact text or naming areas avoids follow-up prompts.

/ commands

Use forward slash in chat to apply commands in RocketUse forward slash in chat to apply commands in Rocket
1

Open the screen you want to edit

Navigate to the page or screen you want to change. / commands automatically target whatever is currently open.
2

Type `/` in the chat input

A popup menu appears with all available commands. Browse the list or start typing to filter.
3

Select a command and add details

Pick a command from the menu, then describe what you want using natural language. Reference sections, elements, or quote exact text.

Phrasing patterns

Replace in place:
  • replace [thing] in [area] with [new thing]
Insert at location:
  • add [thing] to [area]
Edit by text match:
  • change “Old text” to “New text” in [area]
Examples:
  • /Update Content change "Get started" to "Launch now" in hero section
  • /Remove Element testimonial card three in reviews section
  • /Generate Image replace team photo in About section with a modern workspace photo
  • /Fix Layout Issues in pricing grid

Available / commands

Use this catalog to see which / commands each category offers from chat, organized by app type and intent.
Purpose: Change the app name in titles, UI, and metadata.Examples:
  • /Update App Name Nova Suite
  • /Update App Name Atlas
For custom text blocks that still show the old name, use /Update Content.
Purpose: Apply a new color scheme across your entire web app.Examples:
  • /Change App Theme switch to a light theme with navy primary and soft gray background
  • /Change App Theme primary color #4F46E5 and accent #F97316
If colors look off after a big change, follow up with /Fix Theme Switching.
Purpose: Add coordinated light and dark theme options to your app.Examples:
  • /Add Light/Dark Theme
  • /Add Light/Dark Theme with higher contrast dark mode for text and buttons
Use /Fix Theme Switching if toggling between modes does not update all areas.

@ commands

@ command tutorial
1

Trigger the picker

Start your message with @, or insert it anywhere in your sentence. The Files & Folders picker opens in chat.
2

Select your target

Click Files & Folders, search for your file or folder, and select it. Your selection appears in the chat input.
3

Write your instruction

Continue typing. The scope is locked to your selection.

Example patterns

Restructure content: @pages/faq.jsx reorder questions so payments and refunds appear first. keep answers unchanged. Improve guidance: @pages/onboarding.jsx rewrite tips to be friendlier and shorter. keep the same steps. Replace visuals: @assets/screenshots replace getting-started.png with the latest capture. update the caption to match. Clarify microcopy: @components/empty-state rewrite the message to set expectations and add a single call to action. Localize a section: @pages/about.jsx translate the team bio section to Spanish. keep names and roles in English.

Guidelines

Referencing elements

Use clear terms like “hero section”, “footer”, “primary CTA button”, or “pricing image row”. Quote exact text for copy changes: "Get started" to "Launch now". For @ commands, use exact paths: @pages/home.tsx, @components/card, or @docs/faq.md.

Workflow tips

Make content changes first. If reflow causes issues, run /Fix Layout Issues. State locations for clarity: “in hero”, “in pricing”, “navigation bar”. Keep instructions specific and atomic. Small, clear edits work best.

Troubleshooting

Nothing changed:
  • Confirm you are on the correct screen
  • For text: Quote the exact phrase
  • For images: Name the area precisely
Mobile layout issues:
  • Try /Fix Layout Issues for mobile breakpoints
  • If problems persist: Add tablet breakpoint
Cannot find the right file (@ commands):
  • Start typing the exact name in the picker, including the folder path if you know it
Edit feels too broad (@ commands):
  • Split the request into smaller @ command messages, each scoped to a single file or folder

What’s next?