Point, or Let It Look
Point Claude at a file when it holds a decision or a look-alike trap. Otherwise let it search.
Where you'll practice this
3 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.
Point at the Right Teal
Rosa wants a Wholesale link in Copper Kettle's shop header so café buyers can find their price list at `/wholesale`. The header reads its links from `nav-links.ts` and its colors from `theme.ts`. Nadia chose the link's color, "kettle teal", and wrote it into…
Guard the Revenue Reports
Copper Kettle's admin dashboard needs a `GET /api/reports` endpoint that lists the monthly sales reports. These reports show revenue, so only staff may see them. Every existing route uses `authMiddleware`, which lets in any logged-in customer. Ollie, who runs finance and…
Set Up the Empty Repo
June Halvorsen, president of the Harbor Kayak Club (a volunteer paddling club on San Francisco Bay), ran the kickoff call for `tidepool`, a small API (a service other apps ask for data) that will serve tide times for the spots members paddle. The repo is empty except for a…
Other principles in Context
Declare the Tools You Need
Name the connected source and what to do if it's unreachable. Access itself comes from the connection, not the prompt.
Describe Before You Prescribe
Say what happens now and what should happen instead, so Claude changes only the gap.
Describe Relationships
Say how your data connects and what happens on delete. Those are business decisions only you can make.
Explain the Integration Point
Describe the handoff: what starts it, what crosses, and what happens on a failure or a duplicate.
Follow an Existing Pattern
Point at something already done right and ask Claude to match it and reuse it.
Map to Real Components
Ask Claude to reuse the components you already ship, not build look-alike copies.