Write a product description

Product copy that describes what the thing does instead of how excited you are about it. The constraint list is where the work happens.

When to use it

Marketing copy where credibility matters more than enthusiasm, and the reader has seen a hundred landing pages this month.

What it prevents

Superlative soup. Models default to the register of the marketing copy they were trained on, which is the register your sceptical reader has learned to skim past. The banned-words list does more work here than any positive instruction.

The prompt

Write a product description for Acme Sync, a tool that keeps Figma files and production code in step.

### Audience
Frontend developers evaluating tools. They are sceptical of marketing copy and will close the tab if they see any.

### Context
The competing tools require designers to change their workflow. Acme Sync does not.

### Requirements
- Length: About 120 words.
- Output format: Two short paragraphs, no headings.
- Lead with the specific failure it prevents.
- Avoid: superlatives, exclamation marks, and the words seamless, revolutionary, and powerful.

### Example of the wanted output
Your designer moved a button. You found out in code review, three days later...

Why each part is there

Every section of that prompt exists because a specific failure happens without it. These are the checks it passes, and what each one is protecting you from:

• States a concrete task — why this matters
• Avoids vague language — why this matters
• Specifies an output format — why this matters
• Gives context or audience — why this matters
• Avoids dangling references — why this matters
• Includes an example — why this matters
• Separates data from instructions — why this matters
• Avoids over-aggressive phrasing — why this matters
• Defines what a good answer looks like — why this matters

How to adapt this one

Swap the product and the failure it prevents, and rebuild the banned-words list for your category — every industry has its own dead words. Keep the length cap tight; product copy fails long, not short. The “sceptical reader who will close the tab” line is load-bearing: it stops the model reaching for the register of the copy it was trained on.

The mistake this prompt avoids

Listing features instead of the failure the product prevents. “Real-time sync, version history, conflict resolution” is a spec sheet; “your designer moved a button and you found out in code review three days later” is a reason to care. Lead with the pain, name the feature second, and only if it earns its place.

A variation

Writing for an app store or a marketplace listing, where the first line is all most people read? Cut everything after the opening sentence and spend the whole budget getting that one line to name a concrete moment. The constraints matter more, not less, when there is less room to recover.

Check your version

Once you have adapted it, run it through the checker. The same nine checks that graded this page will grade yours, free and in your browser — paste it in, or build one from scratch by answering a few questions.