Prompt template

Product Description

Write product descriptions grounded in provided facts with benefit hierarchy, audience-appropriate language, and SEO-conscious structure.

Product NameProduct DetailsKey FeaturesAudienceTone

chatgptexamplesgrounded_facts

chatgpt variant

Claude-optimized prompt structure shaped for chatgpt.

# Task
Write a product description using ONLY the provided facts. Do not invent specs, claims, or capabilities.

# Inputs
- Product name: {product_name}
- Product details: {product_details}
- Key features: {key_features}
- Audience: {audience}
- Tone: {tone}

# Anti-hallucination rules
1. Every claim must trace back to the provided product details or features.
2. Do not add comparisons to competitors unless provided.
3. Do not invent use cases, statistics, or testimonials.
4. If a feature's benefit is not obvious from the facts, state the feature plainly without speculating on value.
5. Mark any inferred benefits with [INFERRED] so the user can verify.

# Description structure
1. **Headline** (under 70 chars): Benefit-led, includes product name.
2. **Short description** (30-50 words): What it is, who it's for, primary value.
3. **Full description** (100-200 words): Expand on the value, use cases, and differentiators. Write for the stated audience's reading level.
4. **Bullet benefits** (5 items): Each bullet starts with a bolded benefit, followed by the supporting feature. Format: **Benefit** — Feature detail.
5. **SEO keywords**: Suggest 3-5 keywords naturally embedded in the descriptions.

# Output
Return all 5 sections above. Flag any [INFERRED] benefits.

# Task
Write a product description using ONLY the provided facts. Do not invent specs, claims, or capabilities.

# Inputs
- Product name: {product_name}
- Product details: {product_details}
- Key features: {key_features}
- Audience: {audience}
- Tone: {tone}

# Anti-hallucination rules
1. Every claim must trace back to the provided product details or features.
2. Do not add comparisons to competitors unless provided.
3. Do not invent use cases, statistics, or testimonials.
4. If a feature's benefit is not obvious from the facts, state the feature plainly without speculating on value.
5. Mark any inferred benefits with [INFERRED] so the user can verify.

# Description structure
1. **Headline** (under 70 chars): Benefit-led, includes product name.
2. **Short description** (30-50 words): What it is, who it's for, primary value.
3. **Full description** (100-200 words): Expand on the value, use cases, and differentiators. Write for the stated audience's reading level.
4. **Bullet benefits** (5 items): Each bullet starts with a bolded benefit, followed by the supporting feature. Format: **Benefit** — Feature detail.
5. **SEO keywords**: Suggest 3-5 keywords naturally embedded in the descriptions.

# Output
Return all 5 sections above. Flag any [INFERRED] benefits.

claudeexamplesgrounded_facts

claude variant

Claude-optimized prompt structure shaped for claude.

<context>
  <product_name>{product_name}</product_name>
  <product_details>{product_details}</product_details>
  <key_features>{key_features}</key_features>
  <audience>{audience}</audience>
  <tone>{tone}</tone>
</context>
<task>Write a product description using ONLY the provided facts.</task>
<instructions>
  Anti-hallucination: every claim must trace to provided details. No competitor comparisons unless provided. No invented use cases or stats. Mark inferred benefits [INFERRED].

  Structure:
  1. Headline (under 70 chars, benefit-led)
  2. Short description (30-50 words)
  3. Full description (100-200 words, audience-appropriate)
  4. Bullet benefits (5 items: **Benefit** — Feature)
  5. SEO keywords (3-5)
</instructions>
<output>
  Return all 5 sections. Flag any [INFERRED] benefits.
</output>

<context>
  <product_name>{product_name}</product_name>
  <product_details>{product_details}</product_details>
  <key_features>{key_features}</key_features>
  <audience>{audience}</audience>
  <tone>{tone}</tone>
</context>
<task>Write a product description using ONLY the provided facts.</task>
<instructions>
  Anti-hallucination: every claim must trace to provided details. No competitor comparisons unless provided. No invented use cases or stats. Mark inferred benefits [INFERRED].

  Structure:
  1. Headline (under 70 chars, benefit-led)
  2. Short description (30-50 words)
  3. Full description (100-200 words, audience-appropriate)
  4. Bullet benefits (5 items: **Benefit** — Feature)
  5. SEO keywords (3-5)
</instructions>
<output>
  Return all 5 sections. Flag any [INFERRED] benefits.
</output>

geminiexamplesgrounded_facts

gemini variant

Claude-optimized prompt structure shaped for gemini.

Product name: {product_name}
Product details: {product_details}
Key features: {key_features}
Audience: {audience}
Tone: {tone}

Anti-hallucination rules: every claim must trace to provided details. No competitor comparisons unless given. No invented stats. Mark inferred benefits [INFERRED].

Structure:
1. Headline (under 70 chars, benefit-led)
2. Short description (30-50 words)
3. Full description (100-200 words)
4. Bullet benefits (5: **Benefit** — Feature)
5. SEO keywords (3-5)

Based on the entire content above, return all 5 sections. Flag any [INFERRED] benefits.

Product name: {product_name}
Product details: {product_details}
Key features: {key_features}
Audience: {audience}
Tone: {tone}

Anti-hallucination rules: every claim must trace to provided details. No competitor comparisons unless given. No invented stats. Mark inferred benefits [INFERRED].

Structure:
1. Headline (under 70 chars, benefit-led)
2. Short description (30-50 words)
3. Full description (100-200 words)
4. Bullet benefits (5: **Benefit** — Feature)
5. SEO keywords (3-5)

Based on the entire content above, return all 5 sections. Flag any [INFERRED] benefits.