Every model wants a different prompt.

<role>
  You are a B2B content strategist who has shipped
  pricing-page launch posts for developer tools.
</role>

<task>
  Draft a 600-word launch post announcing the new
  pricing page. Lead with what changed for existing
  users, not the feature list.
</task>

<constraints>
  - Sentence case headings, no exclamation marks
  - Name the actual price and what it replaces
  - One concrete before/after example
</constraints>

<output_format>
  Markdown. H2 sections. No preamble.
</output_format>

Anthropic's guidance leans on explicit XML delimiters and a role set before the task, so the rewrite emits tagged blocks rather than headers.

# Role
B2B content strategist. You have shipped pricing-page
launch posts for developer tools.

# Task
Draft a 600-word launch post announcing the new
pricing page.

# Steps
1. Open with what changed for existing users.
2. State the new price and what it replaces.
3. Give one concrete before/after example.
4. Close with a single next action.

# Constraints
- Sentence case headings
- No exclamation marks, no hype adjectives

# Output
Markdown, H2 sections, no preamble.

OpenAI's guidance favours a flat instruction hierarchy with numbered reasoning steps and the output contract stated last.

**Persona**
A B2B content strategist specialising in developer-tool
pricing launches.

**Context**
The product is a Windows desktop utility. Pricing moved
from usage credits to a flat monthly plan. The audience
is existing users who need to know what changed.

**Task**
Write a 600-word launch post for the company blog.

**Constraints**
- Lead with the change, not the feature list
- Name the actual price
- One before/after example
- Sentence case, no exclamation marks

**Format** Markdown with H2 sections.

Google's guidance front-loads persona and context before the instruction, and asks for the constraint block to sit adjacent to the task.

## Instruction
Write a 600-word blog post announcing a new pricing
page for a Windows developer utility.

## Requirements
- Audience: existing users
- Lead with what changed, not the feature list
- State the new monthly price and what it replaces
- Include one before/after example
- Sentence case headings; no exclamation marks
- Output: markdown, H2 sections, no preamble

## Voice
Plain and specific. Assume the reader already knows
the product.

DeepSeek responds best to dense, low-ceremony instructions — the pack strips decorative structure and keeps the requirements as a tight list.

**Brief**
Announce our new pricing page in a 600-word blog post.

**Who's reading**
Existing users of a Windows desktop utility who want to
know whether this costs them more.

**What matters**
- Say what changed, up front, without softening it
- Name the price and what it replaces
- One before/after example
- Take a position on why flat beats credits

**Avoid**
Hype adjectives, exclamation marks, title case.

**Format** Markdown, H2 sections.

Grok's pack keeps the brief conversational and explicitly licenses a point of view, which the model handles better than rigid scaffolding.

## Deliverable
A 600-word markdown post at content/blog/pricing.md

## Task
Announce the move from usage credits to a flat monthly
plan.

## Content requirements
1. Open with the change as it affects existing users
2. State the new price and what it replaces
3. One before/after example
4. Close with a single next action

## Style
- Sentence case headings
- No exclamation marks or hype adjectives
- Frontmatter: title, description, date

Composer is a coding-surface model, so the pack front-loads the concrete deliverable and file target before any prose direction.