Chapter 2 of 6 · 4 practices · 3 min · 4-question quiz
Writing task prompts
The quality of a coding session depends on the first prompt. These practices give the assistant enough to solve the right problem the first time.
Start: Name the files, the scenario and what "fixed" looks like4 practices in this chapter
- 1Name the files, the scenario and what "fixed" looks likeClaude Code's docs show the difference specific context makes: The specific versions do four things: scope the task, point to sources, reference existing patterns and describe the symptom with what…
- 2Separate exploring and planning from writing code on larger changesLetting an assistant jump straight to code can produce a working solution to the wrong problem. Claude Code recommends four phases: Explore: the assistant reads files and answers questions without…
- 3Break large work into small, reviewable tasksGitHub's Copilot guide lists breaking complex tasks into smaller parts as its first prompt tip. Small tasks are easier for the assistant to get right and easier for you to review.
- 4State constraints the assistant would otherwise guess atAssistants fill gaps with reasonable defaults, and reasonable defaults are often not your project's choices. Say up front: libraries: "use only libraries already in package.json"; scope: "change only…
Check yourself on this chapter
4 questions, right here once you are signed in. Your progress is saved as you read.