Prompt Engineer · Sample Output

Prompt Lab

Same task, different wording. On the left: the vague prompts most people actually use. On the right: the rewritten versions — and the outputs each one earned.

This is a sample deliverable from the Prompt Engineer skill. The full methodology, checklists, and reference docs live inside the paid skill. All companies, people, and data below are fictional.
CASE 01

Product description: from "make it nicer" to "ready to publish"

Task: write an e-commerce product description for the fictional brand Nimbus Tea White Peach Oolong. Downstream is a product detail page, facing consumers directly.

Before · Vague version
Write me a product description for white peach oolong tea. Make it appealing, with a premium feel.

Model output (excerpt)

This white peach oolong tea is truly delicious — enchanting aroma, silky smooth taste. One sip and you're transported to a peach orchard. Made from hand-picked premium ingredients with masterful craftsmanship, it's the perfect choice for your daily tea ritual. Don't just be tempted — come taste it now!

✕ Adjective pile-up✕ Zero substance✕ Reads like MLM spam
After · Rewritten
You are a copywriter who has written 200+ food e-commerce product detail pages. Task: write a product description for "Nimbus Tea White Peach Oolong (120g tin)". Rules: 1. 120–160 words, in 3 paragraphs: flavor / craft / drinking occasion. 2. Each paragraph must include at least 1 concrete fact (choose one: origin, process parameter, or brewing suggestion). 3. Banned words: artisanal, exquisite, transported, must-have. 4. End with 1 call-to-action sentence, max 15 words. Example input → output: Input: jasmine green tea 100g Output: [3-paragraph, 140-word example with concrete facts like "Fuding tea gardens," "7 rounds of scenting," "85°C water"] When unsure about a product fact, mark it [TBD] and keep writing — never invent.

Model output

Flavor: Opening the tin releases ripe white peach; the first sip is sweet, then a clean aftertaste — the oolong's roast sits under the fruit, never stealing the show. Cold-brew 6 hours for an even cleaner peach note.
Craft: Northern Fujian high-mountain oolong as the base, blended with dried white peach from a [TBD] orchard, lightly roasted to lock in the fruit. Each 120g tin brews about 15 cups.
Occasion: For the 3 p.m. slump — 85°C water, 2-minute steep; one cup won't touch your sleep tonight.
Can't decide on an afternoon tea? This is it.

✓ Stable structure✓ Concrete facts✓ Publish-ready

What changed

  • Set the acceptance criteria first: word count, paragraph structure, what each paragraph must contain — write it down before writing the prompt, not while nitpicking afterward.
  • Replace adjectives with bans: "premium feel" can't be verified; "never use artisanal / exquisite" can.
  • Give one good example: a model copying an example's shape is more reliable than one "understanding" the rules.
  • Block fabrication: mark uncertain facts [TBD] instead of letting the model "enrich the details" for you.
CASE 02

Meeting notes: from "wall of text" to "action-item table"

Task: turn a fictional weekly-meeting transcript into an action-item list. Downstream is a project-management tool, which needs structured input.

Before · Vague version
Summarize these meeting notes and pull out the to-dos. [notes…]

Model output (excerpt)

The meeting mainly covered the Q4 launch plan. Everyone felt the timeline is tight and departments need to coordinate. Liam will follow up on the design mockups, Maya will look into the data report issue, and Mr. Zhang stressed that quality matters. Next: keep pushing forward.

✕ No owner + deadline✕ Meeting commentary mixed in✕ Can't import into a tool
After · Rewritten
Task: extract action items from the meeting notes below and output a Markdown table. Column definitions (strict): | Item | Owner | Due date | Priority P0–P2 | Rules: 1. Only include people and tasks explicitly mentioned in the notes; for items with no owner, write "Unassigned" in Owner. 2. Prefer explicit dates from the notes for Due date; when the notes only say something vague like "next week," convert it to a concrete date and mark it with *. 3. Put uncertain items in an "Uncertain" section below the table — never inside the table. 4. Don't recap the discussion; output only the table + Uncertain section. Example: Input: [3-line notes example] Output: | Item | Owner | Due date | Priority | | Confirm homepage redesign draft | Liam | 10-14 | P0 | Notes: <paste>

Model output

| Item | Owner | Due date | Priority |
| Confirm homepage redesign final draft | Liam | 10-14 | P0 |
| Fix garbled report export | Maya | 10-12* | P1 |
| Produce Q4 launch checklist | Unassigned | TBD | P1 |

Uncertain: "Quality matters" has no corresponding action item — excluded.

✓ Import-ready✓ No invented owners✓ Uncertain items isolated

What changed

  • Define the table before the content: column names, allowed values, how to fill gaps — the format contract comes first.
  • Give missing info an exit: "Unassigned" and the "Uncertain" section mean the model never has to invent things to deliver.
  • The example is the format: one 3-line example beats three paragraphs of "please output a clear table."