@ command lets you scope a chat instruction to one file or folder using plain references like @components/button or @docs/faq.md.What is @ command?
A targeting feature that confines your instructions to a specific file or folder, preventing unintended changes elsewhere.
Commands
Why use @ command?
Broad prompts can touch unrelated areas or miss your intended target. @ ensures edits stay intentional and accurate with fewer revisions.
Type
@ in chat to open the Files & Folders picker. Search by screen name, folder, or file, then select. Rocket applies your instruction only to that selection.How to use @ command
1
Trigger the picker
Start your message with
@, or insert it anywhere in your sentence.2
Select your target
Click Files & Folders, search for your file or folder, and select it.
3
Write your instruction
Continue typing. The scope is locked to your selection.
After
@ command runs: You’ll see a short summary of the applied change and a preview link.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.
Best use cases
- Precise edits to a known file or folder
- Iterating on isolated components, docs, assets, or configuration
- Preventing changes from affecting unrelated areas
Guidelines
Referencing targets
Use exact paths:@pages/home.tsx, @components/card, or @docs/faq.md. Add brief context when helpful: @components/navbar refine mobile menu text for clarity.
Writing instructions
Keep instructions specific and atomic. Small, clear edits work best. Confirm the correct path in the picker before writing.Post-edit checks
If visual layout on a page is impacted, review the screen and adjust spacing as needed.Troubleshooting
Can’t find the right file: Start typing the exact name in the picker, including the folder path if you know it. Edit feels too broad: Split the request into smaller@ command messages, each scoped to a single file or folder.
Quick reference
| Goal | Example |
|---|---|
| Restructure content | @docs/faq.md reorder questions. keep answers. |
| Refresh guidance | @pages/onboarding.tsx rewrite tips to be friendlier and shorter. |
| Replace asset | @assets/screenshots replace getting-started.png and update its caption. |
| Improve messaging | @components/empty-state clarify message and keep a single CTA. |
| Translate section | @pages/about.tsx translate the team bio section to Spanish. |
Need help?
Email support@rocket.new or ask in our Discord community.
Email support@rocket.new or ask in our Discord community.