Skip to content
Free AI Tools
How toJun 18, 20262 min read

How to write prompts that actually work (without resorting to 'act as…')

Practical prompt patterns for writing, image, and code tools. Stop relying on incantations; structure the brief like you'd brief a colleague.

  • #prompts
  • #writing
  • #workflow

Why most prompt advice stays useless

Most prompt advice online reads like incantations: "act as a senior copywriter with twenty years of experience." That works a little — and it falls apart the second the task gets more specific than "write me a tweet."

A good prompt gives the model the same four pieces of context a sharp colleague would expect:

  1. Audience. Who is this for?
  2. Goal. What should the reader do or feel after this?
  3. Constraints. Tone, length, structure, what to avoid.
  4. Examples. Two short examples beat a paragraph of adjectives.

Five prompt patterns that hold up across tools

1. Brief-style prompt

Write a 600-word blog intro for indie SaaS founders who don't ship landing pages
because they overthink the copy. Tone: blunt but warm. No clichés. End with a
question that invites a real answer, not a CTA.

This is the workhorse. Use it whenever you'd brief a human writer.

2. Reverse brief

Paste an example you like, then describe why.

Here's a paragraph I like (paste it). Use the same pacing and sentence-length
profile, but adapt it to this topic...

3. Section-by-section

For long output, ask the model for an outline first, then per-section drafts. Outlines you can edit are way more useful than drafts you can edit.

4. Constraint prompts

List 10 headlines for X. Each must be under 12 words, contain a number,
and avoid the words "ultimate", "essential", and "powerful".

Constraints force specificity.

5. Critique loop

Here's a draft. Critique it for tone, structure, and weak claims. Suggest
three concrete revisions. I will edit, not you.

The "I will edit, not you" line nudges the model toward review-mode rather than rewriting everything.

What doesn't matter

  • "Act as" framing. It moves the needle a little; structured briefs move it more.
  • Polite language. "Please" and "thank you" don't change output quality.
  • Long system prompts. Most tools strip or compress them. Front-load the most important constraint at the top.

Prompts are briefs, not spells. Treat them that way and you'll spend a tenth of the time producing twice the output.