Back to guide/Developer Tools

Multi-File Editing Task

Claude Code works best when you scope the task clearly and ask for a plan first. The 'ask before installing dependencies' and 'explain plan first' constraints prevent runaway changes. Running tests and lint at the end catches issues before you even review the code.

claude-code-tutorialfeatureDescriptionexpectedFilesrequirements
Edit View
Prompt
Implement the following feature: {{featureDescription}}

**Affected files (likely):** {{expectedFiles}}

**Requirements:**
{{requirements}}

**Constraints:**
- Follow the existing code patterns in this project (check CLAUDE.md)
- Do not modify files outside the scope of this feature
- Maintain all existing tests — if you break one, fix it
- Add TypeScript types for any new interfaces or function signatures
- If you need to install a new dependency, ask me first before proceeding

**Implementation approach:**
1. Read the relevant files first and explain your plan
2. Wait for my approval before making changes
3. Implement changes file by file
4. After all changes, run {{testCommand}} and {{lintCommand}} to verify

Show me a brief plan before you start coding.

Variables to customize

{{featureDescription}}{{expectedFiles}}{{requirements}}{{testCommand}}{{lintCommand}}

Why this prompt works

Claude Code works best when you scope the task clearly and ask for a plan first. The 'ask before installing dependencies' and 'explain plan first' constraints prevent runaway changes. Running tests and lint at the end catches issues before you even review the code.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.