When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.
The document is stored at .claude/product-marketing-context.md.
Workflow
Step 1: Check for Existing Context
First, check if .claude/product-marketing-context.md already exists.
If it exists:
Read it and summarize what's captured
Ask which sections they want to update
Only gather info for those sections
If it doesn't exist, offer two options:
Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
Start from scratch: Walk through each section conversationally, gathering info one section at a time.
Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
Step 2: Gather Information
If auto-drafting:
Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
Draft all sections based on what you find
Present the draft and ask what needs correcting or is missing
Iterate until the user is satisfied
If starting from scratch:
Walk through each section below conversationally, one at a time. Don't dump all questions at once.
For each section:
Briefly explain what you're capturing
Ask relevant questions
Confirm accuracy
Move to the next
Important: Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
Sections to Capture
1. Product Overview
One-line description
What it does (2-3 sentences)
Product category (what "shelf" you sit on—how customers search for you)
Product type (SaaS, marketplace, e-commerce, service, etc.)
Business model and pricing
2. Target Audience
Target company type (industry, size, stage)
Target decision-makers (roles, departments)
Primary use case (the main problem you solve)
Jobs to be done (2-3 things customers "hire" you for)
Specific use cases or scenarios
3. Personas (B2B only)
If multiple stakeholders are involved in buying, capture for each:
