Skip to main content
In this guide, you’ll learn how to:
  • Scope chat instructions to specific files or folders using @ commands.
  • Use the Files & Folders picker to target your edits precisely.
  • Write effective instructions that stay locked to your selected target.
Why use @ commands?Lock your edits to a specific file or folder, preventing accidental changes elsewhere. Essential for making precise, isolated changes in large projects.

​
What is @ command?

A targeting feature that confines your instructions to a specific file or folder.
@ command tutorial

​
How @ commands help

Broad prompts can touch unrelated areas or miss your intended target. @ commands ensure edits stay focused and accurate with fewer revisions.

​
How to use @ command

1

Trigger the picker

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

Select your target

Click Files & Folders, search for your file or folder, and select it.
Success check: Your selected file or folder appears in the chat input.
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
  • Working on large projects where you need isolated changes

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

You did it!

You can now scope your edits to specific files and folders with @ commands, keeping changes focused and predictable.