Product Description Writer
Translate a product's specs into the on-site PDP master copy: benefit-led, scannable, in the brand's voice, decidable in eight seconds on a phone.
Workflow
- Gather inputs. Get the spec/feature list, the target customer, and the brand voice. If voice is unknown, infer it from the category and ask exactly one calibrating question. If the spec list is thin, ask for the one detail competitors omit - do not pad with fluff.
- Find the one reason they buy. Name the core transformation or job-to-be-done, not the product category ("slices a ripe tomato without crushing it," not "knife"). This is the lead hook.
- Translate each spec to a benefit. For every spec write feature + "which means" + benefit ("316 stainless steel, which means it won't rust in a salt-air bathroom"). Keep the spec for credibility, the benefit for desire. Drop any feature that translates to nothing the buyer cares about.
- Surface and answer objections. Name the silent doubt - sizing, fit, durability, returns, "will this work for me" - and give one reassuring line each, woven into bullets or a short "Good to know" note. If it runs small, say so.
- Assemble for the F-pattern scan. Open with the lead hook, then a 2-3 sentence intro, then 3-5 benefit bullets with the payoff word front-loaded and the first 2-4 words bold. Close with a benefit-restating CTA. Put a "Details" or "Specs" block at the bottom for literal numbers, dimensions, materials, and care.
- Calibrate voice. Match sentence length, vocabulary, and warmth to the brand (premium skincare is calm and precise; a snack brand is playful).
Quality bar
- The first line works as a standalone hook - many shoppers read nothing else.
- Every benefit traces to a spec in the source; every spec that survives earns its place.
- Sentences stay under 20 words; bullets front-load the payoff.
- Spec-hunters can find every literal number in the Details block without it cluttering the sell.
- Every objection a buyer would have before adding to cart is answered honestly.
Deliverable
Produce the complete PDP master copy as one paste-ready block: lead hook line, 2-3 sentence intro, 3-5 benefit bullets (payoff front-loaded, opening words bold), objection-handling lines or a "Good to know" note, a benefit-restating CTA, and the Details/Specs block with every literal number, dimension, material, and care instruction from the source. Flag any spec you dropped and why, and any claim you could not support from the inputs.
Do NOT
- Do not invent performance numbers, certifications, materials, or health/safety/earnings claims. Use only what the source provides; if asked to claim an outcome the source doesn't support, refuse and offer a compliant alternative.
- Do not open with "premium quality" or any generic category claim.
- Do not fabricate scarcity, countdowns, or low-stock urgency. Use urgency only when it is true (limited batch, seasonal, real low stock).
- Do not keep features that translate to no buyer benefit.
- Do not end with a bare "Buy now" - restate the benefit in the CTA.
1---2name: product-description-writer3description: Writes the single on-site PDP master copy - a benefit-led, scannable product detail page in the brand's voice - from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings - use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants - use variant-copy-scaler instead.4---5# Product Description Writer67Translate a product's specs into the on-site PDP master copy: benefit-led, scannable, in the brand's voice, decidable in eight seconds on a phone.89## Workflow10111. Gather inputs. Get the spec/feature list, the target customer, and the brand voice. If voice is unknown, infer it from the category and ask exactly one calibrating question. If the spec list is thin, ask for the one detail competitors omit - do not pad with fluff.122. Find the one reason they buy. Name the core transformation or job-to-be-done, not the product category ("slices a ripe tomato without crushing it," not "knife"). This is the lead hook.133. Translate each spec to a benefit. For every spec write feature + "which means" + benefit ("316 stainless steel, which means it won't rust in a salt-air bathroom"). Keep the spec for credibility, the benefit for desire. Drop any feature that translates to nothing the buyer cares about.144. Surface and answer objections. Name the silent doubt - sizing, fit, durability, returns, "will this work for me" - and give one reassuring line each, woven into bullets or a short "Good to know" note. If it runs small, say so.155. Assemble for the F-pattern scan. Open with the lead hook, then a 2-3 sentence intro, then 3-5 benefit bullets with the payoff word front-loaded and the first 2-4 words bold. Close with a benefit-restating CTA. Put a "Details" or "Specs" block at the bottom for literal numbers, dimensions, materials, and care.166. Calibrate voice. Match sentence length, vocabulary, and warmth to the brand (premium skincare is calm and precise; a snack brand is playful).1718## Quality bar1920- The first line works as a standalone hook - many shoppers read nothing else.21- Every benefit traces to a spec in the source; every spec that survives earns its place.22- Sentences stay under 20 words; bullets front-load the payoff.23- Spec-hunters can find every literal number in the Details block without it cluttering the sell.24- Every objection a buyer would have before adding to cart is answered honestly.2526## Deliverable2728Produce the complete PDP master copy as one paste-ready block: lead hook line, 2-3 sentence intro, 3-5 benefit bullets (payoff front-loaded, opening words bold), objection-handling lines or a "Good to know" note, a benefit-restating CTA, and the Details/Specs block with every literal number, dimension, material, and care instruction from the source. Flag any spec you dropped and why, and any claim you could not support from the inputs.2930## Do NOT3132- Do not invent performance numbers, certifications, materials, or health/safety/earnings claims. Use only what the source provides; if asked to claim an outcome the source doesn't support, refuse and offer a compliant alternative.33- Do not open with "premium quality" or any generic category claim.34- Do not fabricate scarcity, countdowns, or low-stock urgency. Use urgency only when it is true (limited batch, seasonal, real low stock).35- Do not keep features that translate to no buyer benefit.36- Do not end with a bare "Buy now" - restate the benefit in the CTA.
SkillMedev