niahere 0.2.52 → 0.2.56

package/skills/product-marketing-context/SKILL.md

@@ -0,0 +1,241 @@
+---
+name: product-marketing-context
+description: "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,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context."
+metadata:
+  version: 1.1.0
+---
+
+# Product Marketing Context
+
+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 `.agents/product-marketing-context.md`.
+
+## Workflow
+
+### Step 1: Check for Existing Context
+
+First, check if `.agents/product-marketing-context.md` already exists. Also check `.claude/product-marketing-context.md` for older setups — if found there but not in `.agents/`, offer to move it.
+
+**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:**
+
+1. **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.
+
+2. **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:**
+1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
+2. Draft all sections based on what you find
+3. Present the draft and ask what needs correcting or is missing
+4. 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:
+1. Briefly explain what you're capturing
+2. Ask relevant questions
+3. Confirm accuracy
+4. Move to the next
+
+Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.
+
+---
+
+## 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:
+- User, Champion, Decision Maker, Financial Buyer, Technical Influencer
+- What each cares about, their challenge, and the value you promise them
+
+### 4. Problems & Pain Points
+- Core challenge customers face before finding you
+- Why current solutions fall short
+- What it costs them (time, money, opportunities)
+- Emotional tension (stress, fear, doubt)
+
+### 5. Competitive Landscape
+- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)
+- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
+- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)
+- How each falls short for customers
+
+### 6. Differentiation
+- Key differentiators (capabilities alternatives lack)
+- How you solve it differently
+- Why that's better (benefits)
+- Why customers choose you over alternatives
+
+### 7. Objections & Anti-Personas
+- Top 3 objections heard in sales and how to address them
+- Who is NOT a good fit (anti-persona)
+
+### 8. Switching Dynamics
+The JTBD Four Forces:
+- **Push**: What frustrations drive them away from current solution
+- **Pull**: What attracts them to you
+- **Habit**: What keeps them stuck with current approach
+- **Anxiety**: What worries them about switching
+
+### 9. Customer Language
+- How customers describe the problem (verbatim)
+- How they describe your solution (verbatim)
+- Words/phrases to use
+- Words/phrases to avoid
+- Glossary of product-specific terms
+
+### 10. Brand Voice
+- Tone (professional, casual, playful, etc.)
+- Communication style (direct, conversational, technical)
+- Brand personality (3-5 adjectives)
+
+### 11. Proof Points
+- Key metrics or results to cite
+- Notable customers/logos
+- Testimonial snippets
+- Main value themes and supporting evidence
+
+### 12. Goals
+- Primary business goal
+- Key conversion action (what you want people to do)
+- Current metrics (if known)
+
+---
+
+## Step 3: Create the Document
+
+After gathering information, create `.agents/product-marketing-context.md` with this structure:
+
+```markdown
+# Product Marketing Context
+
+*Last updated: [date]*
+
+## Product Overview
+**One-liner:**
+**What it does:**
+**Product category:**
+**Product type:**
+**Business model:**
+
+## Target Audience
+**Target companies:**
+**Decision-makers:**
+**Primary use case:**
+**Jobs to be done:**
+-
+**Use cases:**
+-
+
+## Personas
+| Persona | Cares about | Challenge | Value we promise |
+|---------|-------------|-----------|------------------|
+| | | | |
+
+## Problems & Pain Points
+**Core problem:**
+**Why alternatives fall short:**
+-
+**What it costs them:**
+**Emotional tension:**
+
+## Competitive Landscape
+**Direct:** [Competitor] — falls short because...
+**Secondary:** [Approach] — falls short because...
+**Indirect:** [Alternative] — falls short because...
+
+## Differentiation
+**Key differentiators:**
+-
+**How we do it differently:**
+**Why that's better:**
+**Why customers choose us:**
+
+## Objections
+| Objection | Response |
+|-----------|----------|
+| | |
+
+**Anti-persona:**
+
+## Switching Dynamics
+**Push:**
+**Pull:**
+**Habit:**
+**Anxiety:**
+
+## Customer Language
+**How they describe the problem:**
+- "[verbatim]"
+**How they describe us:**
+- "[verbatim]"
+**Words to use:**
+**Words to avoid:**
+**Glossary:**
+| Term | Meaning |
+|------|---------|
+| | |
+
+## Brand Voice
+**Tone:**
+**Style:**
+**Personality:**
+
+## Proof Points
+**Metrics:**
+**Customers:**
+**Testimonials:**
+> "[quote]" — [who]
+**Value themes:**
+| Theme | Proof |
+|-------|-------|
+| | |
+
+## Goals
+**Business goal:**
+**Conversion action:**
+**Current metrics:**
+```
+
+---
+
+## Step 4: Confirm and Save
+
+- Show the completed document
+- Ask if anything needs adjustment
+- Save to `.agents/product-marketing-context.md`
+- Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it."
+
+---
+
+## Tips
+
+- **Be specific**: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
+- **Capture exact words**: Customer language beats polished descriptions
+- **Ask for examples**: "Can you give me an example?" unlocks better answers
+- **Validate as you go**: Summarize each section and confirm before moving on
+- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)

package/skills/product-marketing-context/evals/evals.json

@@ -0,0 +1,85 @@
+{
+  "skill_name": "product-marketing-context",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I want to set up my product marketing context. We're a B2B SaaS company that sells a customer feedback platform to product teams.",
+      "expected_output": "Should check if .agents/product-marketing-context.md already exists. If not, should offer two options: (1) Auto-draft from codebase (recommended) or (2) Start from scratch. If user chooses start from scratch, should walk through sections conversationally one at a time. Should cover all applicable sections: Product Overview, Target Audience, Personas, Problems You Solve, Competitive Landscape, Differentiation, Objections, Switching Dynamics, Customer Language, Brand Voice, Proof Points, and Goals. Should create the file at .agents/product-marketing-context.md when complete.",
+      "assertions": [
+        "Checks for existing product-marketing-context.md",
+        "Offers two options: auto-draft or start from scratch",
+        "Covers applicable sections",
+        "Walks through sections conversationally one at a time",
+        "Creates file at .agents/product-marketing-context.md"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Update our product marketing context. We just added a new enterprise tier and our target audience has expanded to include VP of Engineering, not just Product Managers.",
+      "expected_output": "Should check for existing .agents/product-marketing-context.md and read it. Should identify which sections need updating based on the changes: Target Audience (add VP of Engineering), Personas (add new persona), Product Overview (new enterprise tier, including pricing updates within that section), Objections (enterprise-specific), and Competitive Landscape (enterprise competitors). Should update only the relevant sections, preserving existing content that hasn't changed.",
+      "assertions": [
+        "Reads existing product-marketing-context.md",
+        "Identifies sections that need updating",
+        "Updates Target Audience with VP of Engineering",
+        "Adds new persona for the expanded audience",
+        "Updates Product Overview for enterprise tier",
+        "Preserves unchanged sections"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "create a product context doc for my app. it's a mobile app that helps people find hiking trails. we're just getting started.",
+      "expected_output": "Should trigger on casual phrasing. Should check for existing context doc. Should offer auto-draft or start-from-scratch options. Should adapt questions for an early-stage B2C mobile app (outdoor/fitness niche). Should note that some sections may be sparse for an early-stage product and that's okay — they can be filled in as the business matures. Should skip non-applicable sections (e.g., Personas section is B2B-focused) rather than forcing all 12. Should accept lighter answers for sections like Proof Points or Competitive Landscape if the company is new.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Checks for existing context doc",
+        "Offers auto-draft or start-from-scratch options",
+        "Adapts questions for early-stage B2C mobile app",
+        "Notes some sections may be sparse early on",
+        "Skips non-applicable sections rather than forcing all 12",
+        "Creates file at .agents/product-marketing-context.md"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Can you auto-draft our product marketing context from our existing codebase and marketing materials?",
+      "expected_output": "Should activate the auto-draft workflow mode. Should scan the codebase for existing marketing context: README, landing page copy, pricing page, about page, meta descriptions, any existing documentation. Should draft the product-marketing-context.md from what it finds, filling in sections where information is available and flagging sections that need manual input. Should present the draft for review before saving.",
+      "assertions": [
+        "Activates auto-draft workflow mode",
+        "Scans codebase for existing marketing materials",
+        "Drafts context from found information",
+        "Flags sections needing manual input",
+        "Presents draft for review before saving"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Do we have a product marketing context set up? I want to make sure the other marketing skills have context about our product.",
+      "expected_output": "Should check for .agents/product-marketing-context.md (and the older .claude/product-marketing-context.md location). Should report whether it exists and summarize its contents if found. If it doesn't exist, should offer to create one and explain why it's valuable (other skills like copywriting, page-cro, seo-audit check for it first). Should explain how other skills use this context document.",
+      "assertions": [
+        "Checks both file locations",
+        "Reports whether context doc exists",
+        "Summarizes contents if found",
+        "Offers to create if missing",
+        "Explains how other skills use it"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Write homepage copy for our SaaS product.",
+      "expected_output": "Should recognize this is a copywriting task, not a product marketing context task. Should check for product-marketing-context.md (as other skills do), and if it doesn't exist, may suggest creating one first. But should defer to the copywriting skill for actually writing the homepage copy.",
+      "assertions": [
+        "Recognizes this as a copywriting task",
+        "May check for or suggest creating product-marketing-context.md",
+        "References or defers to copywriting skill for the actual copy",
+        "Does not attempt to write homepage copy using context creation patterns"
+      ],
+      "files": []
+    }
+  ]
+}