Coding with AI tools

Stage 2 · Lesson 6 of 6

Pointing the tool at the right files

Setup and project context

You get faster, more accurate answers when you name exactly what the tool should read rather than describing where code lives. In Claude Code, type @ and a path to reference a file, and start a line with ! to run a command whose output joins the conversation.

In Cursor, @ attaches files, folders, @Terminals output or @Branch, your 's with main, and Cmd+Shift+L or Ctrl+Shift+L adds selected code to chat. In Copilot chat, # adds context such as #file or #selection, and @terminal asks about the terminal.

Point at the file to change, a file showing the pattern to follow, and the error you are fixing. If you do not know which files matter, let the tool search.

Common trapattaching the whole to be safe, which buries the file that matters.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with

Keep handy

  • Custom instructions, .instructions.md files and prompt files, as VS Code implements them

  • The shared format your tool can read, with examples of what to put in it

Also worth your time

Mark this stage as not done?