First week with Claude: pitfalls and how to avoid them

1. Asking for a rewrite of everything

Huge rewrite requests create diffs you cannot review. Ask for the smallest change that proves progress, then iterate.

2. Accepting edits you did not read

If you cannot explain the change in one sentence, reject it and ask for a smaller patch plus an explanation.

3. Skipping a baseline backup

Without git or a zip, a bad edit feels catastrophic. Baseline first, experiment second.

4. Tool thrash

Jumping between chat, Code, and new extensions burns the week. Pick one loop for 48 hours. See when to use which.

5. Vague “make it better”

Define better: faster load, clearer copy, fewer bugs, or a specific feature. Constraints make Claude useful.

6. Ignoring verification

Run, click, or test after every change. Unverified green checkmarks are not progress.

Recovery playbook

1. Restore the last good baseline.
2. Write a one-sentence goal.
3. Ask for a file map only.
4. Request one change with a done-when check.
5. Log the lesson in your daily notes.

Use the checklist to stay on rails, then pull prompts from the library.