Loading…
Loading…
The expensive mistakes in data work are rarely syntax errors. They are the join that silently doubled every row, the NULL that quietly dropped a fifth of the customers, and the number in a deck that nobody can reproduce six weeks later. These prompts are built around that: they ask for the failure mode before the answer, insist on a row-count sanity check, and require the model to state its assumptions about your schema rather than inventing columns and moving on. Several are deliberately run before you execute anything.
36 prompts in 5 groups
Drafting SQL from a plain question, making an inherited query legible, and moving it between dialects.
Catching the join that duplicates rows, the NULL that drops them, and the GROUP BY that lies.
Diagnosing a slow query, reading the plan, and finding the smallest index that fixes it.
Designing tables, migrating them without breaking live code, and cleaning what you have been handed.
Pinning down what a metric means, what a report measures, and whether a surprising number is real.
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt