Turn repeated requests into a template

Turn this repeated request into a reusable template.

1. **Compare the examples and separate what changes from what stays.** *What stays is the template. What changes becomes a variable*
2. **Name each variable for what it is, not for one example's value.** `{{industry}}`, not `{{cafe}}`
3. **Mark which variables are required and which are optional**, and **what the template does when an optional one is empty** — ***not "guess", but a stated behavior***
4. **Where two examples differ in output quality, find the instruction that caused it** and keep the better one

**Also report:**
- **Variables that look the same but are not.** *If "tone" sometimes means formality and sometimes means length, splitting them is the whole point of doing this*
- **The part I have been retyping each time that should be fixed in the template**
- **What the template cannot cover** — the cases you would still write by hand

Output: the template with its variables / a table of variable / meaning / required / behavior when empty / one filled example.