Before changing code, make the task clear
Useful coding collaboration starts with a shared understanding. Agree on what should change and how to verify it before editing.
Describe a coding task with a clear scope and acceptance criteria.
01Before you begin
Use a practice project you have permission to work on, and make sure you can restore the original code. This lesson covers task descriptions, not installation.
02Try it together
Ask for reading and analysis first. Once you understand the proposal, you can arrange the changes. This helps surface missing conditions and unintended effects.
Read the README and the form-related code in this project. Goal: show a clear error when the email field is blank before submission. First explain the current behavior, the files you suggest changing, and how you would verify the result. For this turn, analyze only; do not change code.
Make this example fit your own task. Start simple, then adjust.
03How do you know it worked?
Check that the plan points to real files, explains existing behavior, and includes meaningful verification. A plausible-looking plan alone is not enough.
04Now it’s your turn.
Write a small task for a practice project. State the goal, the boundaries, and the acceptance criteria.
When you’re done, take a moment to check:
Official reference: Claude Help Center ↗