Use prompt moves that transfer

First, orient the model with the real audience and decision. Second, ground it in supplied sources. Third, constrain scope, format, and forbidden actions. Fourth, inspect by asking for assumptions, unsupported claims, or tests. Applied to this topic, those moves support turn a verified meal-prep class brief into a truthful two-variant email test, not vague content generation.

Use only these facts: two-hour in-person class; ingredients included; participants leave with five recipes. Audience: busy cooking beginners. Draft a subject line and email under 140 words with one sign-up CTA. Do not claim savings, health outcomes, superiority, scarcity, or testimonials. Then make variant B by changing only the angle from convenience to confidence.

The likely useful output is: Two compact emails with the same offer and CTA; each claim maps to the brief, while the changed angle is explicitly labeled as the sole test variable. Follow with a critic pass, not a request to “improve it”:

Audit the draft against the original contract. Return a table:
criterion | pass/fail | exact evidence | smallest correction.
Do not introduce new facts. List unresolved questions separately.

This second prompt changes the mode from creation to inspection. For alternatives, request deliberately different options and specify the axis of difference. For revision, name one defect and freeze everything else. For extraction, require a schema and define unknown/null behavior. For decisions, ask for criteria, evidence, assumptions, and sensitivity—not hidden private reasoning.

A useful response would look like this: Two compact emails with the same offer and CTA; each claim maps to the brief, while the changed angle is explicitly labeled as the sole test variable. That description is intentionally observable. “Looks good” is not acceptance. The operator must trace every factual phrase to the approved brief, check link and disclosure requirements, review accessibility and brand voice, then measure the predeclared conversion event. Keep the source material beside the draft so review means comparison, not memory.

Do not confuse fluent explanations with evidence. Generation volume is not strategy. A useful campaign has a defensible promise, a specific audience action, and a test that can teach one thing. The prompt is successful only when the resulting artifact survives an external check.

Watch for fabricated urgency; fake statistics; multiple variables changed; vague CTA; stereotyped audience language; optimization without a hypothesis. If the answer is too broad, shrink the deliverable. If it invents, tighten “use only” boundaries and require source labels. If formatting drifts, provide a short valid example and validate mechanically. If every option sounds alike, define meaningful axes. If revision damages good sections, quote the exact passage to preserve.

Keep prompt versions with short notes: what changed, why, and what happened. That creates transferable knowledge. Copying a “perfect prompt” without its data, risk level, and reviewer rarely does.