Nicely done ✓
Here's what strong answers tend to have in common:
- Q1 — State the stack and the finish line up front: e.g. "a Node/Express service backed by Postgres, with a
POST /shortenendpoint, a redirect route, and a per-link click counter," then ask it to scaffold it, run it, and show you it working. - Q2 — There's no single right answer — clear goals, rich context, small steps, and catching mistakes early all pull their weight. The common thread: give the agent a way to tell whether it's on track.
- Q3 — Interrupt, narrow the scope, and point at the source of truth: "Stop — leave those files alone and revert them. Only touch
X, and confirm the plan with me before editing." - In general — a strong prompt hands the agent a goal, the constraints, and a way to check its own work — not just a task.