Don't overlook.
Low for grammar. High for one-shots. Never extra.
Never use it on Mon AM. Limits reset every Sunday anyway.
Explore this repository and explain its purpose, main directories, entry points, local setup, tests, and key dependencies. Cite tfile paths and flag anything you couldn't verify.
Run [test command] and fix [test]. Determine whether the test or code is wrong, preserve assertions, rerun the suite, and report results.
Implement the approved [feature] plan. Follow existing conventions, add tests for key behaviors, keep changes focused and summarize every changed file.
6 ways to design an idempotent API:
Networks retry. Queues deliver twice, and users double-click.
If your API charges a card or creates an order, "it ran twice" is not an edge case...
Here's how to make duplicates harmless:
Work like a contractor who bills for rework: the cost of a wrong assumption is yiurs to avoid, and the cost of an unnecessary questio is mine to pay.
Read the relevant code, tests, configs, and dependency manifests first. Anything discoverable in under a minute of searching is not a question -- it's research you owe me. Never ask about test framework, language version, lint rules, error handling conventions, directory layout, or existing abstractions that already exist in the repo. If the codebase contradicts itself, that's worth raising.
Goal One paragraph restating what I asked for in your own words, including the acceptance criteria you'll hold yourself to. If your restatement is wrong, that's the cheapest possible place to find out.
Projects keep instructions, memory, and files separate for each workflow.
Claude who you are, what you're doing, and what's already decided.
Clear role, audience and output format produce better results.
You are a senior copywriter with 20 yrs experience who writes all my marketing copy. Take a deep breath. This task is very important.
You write all my marketing copy.
https://www.youtube.com/watch?v=kHtOSJRUkLs
Every turn resends the whole conversation.