Reflexion · self-critique
The model writes, then critiques its own draft like a harsh editor, then rewrites.
When to use: Important texts: offers, landing pages, applications, emails to decision-makers.
Task: [WHAT SHOULD BE WRITTEN — e.g. proposal, landing page copy, email].
Audience: [WHO READS IT]. Goal: [WHAT THEY SHOULD DO OR FEEL].
Step 1 — Write a first draft.
Step 2 — Switch roles: you are a demanding senior editor. List the 5 biggest weaknesses of the draft (clarity, persuasion, structure, tone, missing facts). Be specific and blunt.
Step 3 — Rewrite the text fixing every weakness.
Step 4 — Give a one-line summary of what changed and why the new version is better.
Output only steps 3 and 4 unless I ask for the full process.
Acknowledge → solve → next step
Calm, human and concrete — without empty apologies or promises you can’t keep.
When to use: Complaints, bad reviews, delayed orders, billing mistakes.
Write a reply to this customer message: [PASTE THE CUSTOMER MESSAGE]
What actually happened: [THE FACTS FROM OUR SIDE]
What we can offer: [SOLUTION, DISCOUNT, DEADLINE — or "nothing beyond an apology"]
Channel and tone: [EMAIL / GOOGLE REVIEW / SOCIAL MEDIA — formal or friendly]
Structure:
1. Acknowledge the specific problem in the customer’s words (no generic "we apologise for any inconvenience").
2. Explain briefly and honestly what happened — no excuses, no blaming others.
3. The concrete solution and when it will happen.
4. One clear next step and a named contact.
Keep it under 150 words. Do not promise anything that is not listed in "What we can offer". Then give a second, shorter version for a public review reply.
Plain-language rewrite
Rewrites contracts, rules or technical text so anyone understands it — without changing the meaning.
When to use: Explaining terms to customers, rules to employees, or a letter from an authority to a family member.
Rewrite this text in plain language for [READERS — e.g. customers without legal knowledge, a 14-year-old, older people]:
[PASTE THE TEXT]
Rules:
- Short sentences (max. 20 words), everyday words, active voice, "you" instead of "the user".
- Keep every obligation, number, deadline and condition — do not soften or drop anything.
- Explain each unavoidable technical term in brackets the first time.
- Structure: "In short" (2 sentences), then "What this means for you" as bullets, then "Watch out for" (deadlines, costs, risks).
- After the rewrite, list anything you had to interpret, so a lawyer or expert can check it.
Hook · story · value
Three variants with different hooks for LinkedIn or Facebook — no buzzwords, no emoji spam.
When to use: Announcing a project, a new hire, a lesson learned or an event.
Write a post for [LINKEDIN / FACEBOOK / INSTAGRAM] about: [TOPIC AND THE MAIN MESSAGE]
Author and audience: [WHO WRITES IT, WHO SHOULD READ IT]
Facts to include: [NUMBERS, NAMES, DATES]
Write 3 variants, each with a different first line:
A) a surprising fact or number, B) a short personal story, C) a direct question to the reader.
Each variant: 80–150 words, short paragraphs, one concrete lesson or benefit, one clear call to action, max. 2 emoji and 3 hashtags.
Avoid clichés ("I'm thrilled to announce", "game-changer", "in today's fast-paced world").
Finally say which variant you would publish and why.