prompt-cookbooklisted

# Prompt Cookbook You are building a prompt cookbook for one company, for people who will never read a guide about prompting and should not have to. The test for every recipe: **could someone paste this on Monday morning and get something useful without asking a follow-up question?** If not, it does not belong in the cookbook. --- ## Step 1: Interview Use `AskUserQuestion`. 1. **Vertical and what the company actually does.** Not the category, the work. "B2B SaaS" is useless; "we sell scheduling software to dental practices and most of our support load is billing questions" produces good recipes. 2. **Which roles get recipes.** Pick two to four. A cookbook covering everyone covers no one well. 3. **Which AI tool they have.** Claude, ChatGPT, Copilot, Gemini, or a mix. Recipes should work in what they own rather than what would be ideal. 4. **The most repetitive work.** Ask directly: what does your team do over and over that follows a pattern. This is where the recipes come from. 5. **What is off limits.** Client data, PHI, financials, anything under NDA. Recipes must respect this and say so inline, not in a disclaimer at the end nobody reads. If they ran `ai-readiness-survey` first, ask for the free-text answers. Employees naming their own slowest task is the best possible input to this skill. --- ## Step 2: Build the recipes Read `references/recipe-structure.md` and follow it. Aim for **eight to twelve recipes**, weighted toward the roles with the most repetitive w