Recipes
Five questions, start to finish. Each gives the order to call the tools in, what to check at each step, and where the answer comes from.
| Recipe | The question behind it |
|---|---|
| Why is my drawer not showing? | Shoppers should be seeing the drawer and are not |
| Is the drawer earning? | Which features are actually making money |
| What text does the drawer show? | Which wording is live, in which language |
| Add an upsell rule | Recommend a product when another is in the cart (read and write) |
| Add a reward tier | Add a goal to the reward bar (read and write) |
The shape they share
- Start with the tool that reaches a conclusion.
get_setup_healthhands back a verdict with reasons; reading it first usually ends the investigation in one call. - Narrow before you widen. One section, one language. Results are capped at 16,000 characters, and a broad call that gets truncated is worse than a narrow one that does not.
- Take the store's word for it. Timezone and currency come back in the result. Read them.
- Read, then write, then read back. A change should follow a read of the current state and be confirmed by another.
- Say what was not checked. A skipped step or a truncated result belongs in the answer.