Summary  
This chapter covers how to scope prompts for an AI code assistant by specifying which files or folders to inspect, restricting edits to only relevant code, and requesting a brief plan before implementing changes.

General domain of usage  
Debugging authentication code and reviewing related files.

### Keeping Claude Focused

Claude Code can inspect many files, but it does not always need the entire project. Giving it a clear scope helps reduce unnecessary work and keeps its response focused.

Mention the relevant file, folder, or feature directly in your prompt. You can also tell Claude what not to change.


> **Review the authentication files only. Identify the cause of the error, explain your proposed fix, and do not edit unrelated files.**

For larger tasks, ask Claude to inspect the project and create a plan before making changes. This gives you a chance to correct its understanding before it starts working.

> ### Task
>
> * Ask Claude to complete a small task in the provided workspace.
> * Specify which file or folder it should focus on.
> * Tell it not to edit unrelated files.
> * Ask for a short plan before it makes changes.
> * Review whether Claude stayed within the requested scope.


Learn how to use Claude Code to plan, build, improve, and automate a practical business application. You will set up an effective project environment, give Claude reliable context, turn specifications into working features, create reusable skills, connect external tools, and schedule recurring processes.

Explore how Claude Code works, install it locally, and use it to complete your first practical tasks. Learn how project context improves its results and how to refine and deploy what it creates.