v1.0

2026-03-02 00:36:23 +01:00
parent 61004d0c4e
commit 77dbdfa1b9
118 changed files with 11087 additions and 0 deletions
@@ -0,0 +1,98 @@
+---
+description: Brainstorm marketing ideas, positioning, value prop statements, and product names — creative marketing toolkit
+argument-hint: "<product or marketing challenge>"
+---
+
+# /market-product -- Marketing Creative Toolkit
+
+Generate creative marketing assets: campaign ideas, positioning statements, value prop copy, and product naming options. All in one workflow or pick specific modules.
+
+## Invocation
+
+```
+/market-product AI scheduling tool for remote teams — need launch marketing
+/market-product Help me position our analytics product against enterprise competitors
+/market-product We need a name for our new developer productivity feature
+```
+
+## Workflow
+
+### Step 1: Understand the Marketing Need
+
+Ask:
+- What is the product? Target audience?
+- What do you need? (full marketing toolkit, or specific: ideas, positioning, naming, copy)
+- What's the context? (launch, rebrand, campaign, competitive repositioning)
+- Any existing brand guidelines or tone of voice?
+
+### Step 2: Generate Based on Need
+
+**Marketing Ideas** — apply **marketing-ideas** skill:
+- 5 creative, cost-effective campaign ideas
+- Each with: channel, messaging angle, engagement rationale, estimated effort
+- Mix of quick wins and bigger bets
+
+**Positioning** — apply **positioning-ideas** skill:
+- Identify top 5 competitors for positioning context
+- Generate 3-5 positioning statements differentiated from each
+- Include rationale for each positioning angle
+
+**Value Proposition Statements** — apply **value-prop-statements** skill:
+- Generate copy for marketing, sales, and onboarding contexts
+- Segment-specific variations
+- Short (tagline), medium (elevator pitch), and long (landing page) versions
+
+**Product Naming** — apply **product-name** skill:
+- Brainstorm 5 unique, memorable names
+- Each with: rationale, brand alignment, domain availability notes
+- Check for unintended meanings or conflicts
+
+### Step 3: Generate Output
+
+```
+## Marketing Toolkit: [Product]
+
+**Date**: [today]
+**Context**: [launch / rebrand / campaign / etc.]
+
+### Marketing Campaign Ideas
+| # | Idea | Channel | Effort | Expected Impact |
+|---|------|---------|--------|----------------|
+
+### Positioning Options
+| # | Positioning | vs Competitor | Strength | Risk |
+|---|-----------|--------------|----------|------|
+
+**Recommended positioning**: [which and why]
+
+### Value Prop Copy
+**Tagline**: [one line]
+**Elevator pitch**: [2-3 sentences]
+**Landing page hero**: [headline + subheading]
+**Sales one-liner**: [for sales conversations]
+
+### Product Name Options (if requested)
+| # | Name | Rationale | Domain | Risk |
+|---|------|----------|--------|------|
+
+### Messaging Matrix
+| Audience | Key Message | Proof Point | CTA |
+|----------|-----------|------------|-----|
+```
+
+Save as markdown.
+
+### Step 4: Offer Next Steps
+
+- "Want me to **draft full marketing content** (blog post, email, social)?"
+- "Should I **define the North Star metric** for this campaign?"
+- "Want me to **create a competitive battlecard** to support positioning?"
+- "Should I **plan the full launch**?"
+
+## Notes
+
+- Positioning should be tested, not assumed — recommend A/B testing headlines
+- Value prop copy should use the customer's language, not internal jargon
+- Marketing ideas should be specific and actionable, not generic ("use social media")
+- Product names should be checked for trademark conflicts before committing
+- Always tie marketing back to customer JTBD, not product features
@@ -0,0 +1,113 @@
+---
+description: Define your North Star Metric and supporting input metrics — classify the business game and validate against best practices
+argument-hint: "<product or business>"
+---
+
+# /north-star -- North Star Metric Definition
+
+Identify the single metric that best captures the value your product delivers, plus the input metrics that drive it. Classifies your business game and validates against proven criteria.
+
+## Invocation
+
+```
+/north-star B2B SaaS for team collaboration
+/north-star Consumer fitness app monetized through subscriptions
+/north-star Help me fix our North Star — we're tracking DAU but it doesn't feel right
+```
+
+## Workflow
+
+### Step 1: Understand the Product
+
+Ask:
+- What is the product? What value does it deliver to users?
+- What's the business model? (subscription, transaction, advertising, marketplace)
+- Current metrics being tracked (if any)
+- Why is this needed now? (new product, existing metric feels wrong, team alignment)
+
+### Step 2: Classify the Business Game
+
+Apply the **north-star-metric** skill:
+
+Identify which game the product is playing:
+- **Attention**: Revenue from user time/engagement (media, social, ad-supported)
+- **Transaction**: Revenue from purchases (e-commerce, marketplace)
+- **Productivity**: Revenue from efficiency gains (SaaS, tools, B2B)
+
+The game determines what kind of North Star makes sense.
+
+### Step 3: Define the North Star
+
+- Propose 2-3 North Star candidates
+- Validate each against 7 criteria:
+  1. Expresses value delivered to customers
+  2. Is a leading indicator of revenue
+  3. Is measurable and trackable
+  4. Is understandable by the whole team
+  5. Is actionable (teams can influence it)
+  6. Is not a vanity metric
+  7. Is not gameable without delivering real value
+- Recommend the strongest candidate with rationale
+
+### Step 4: Define Input Metrics
+
+For the selected North Star, identify 3-5 input metrics:
+- Each input metric should be a lever that directly drives the North Star
+- Each should be ownable by a specific team
+- Together, inputs should be MECE in explaining North Star movement
+
+### Step 5: Generate Metrics Framework
+
+```
+## North Star Framework: [Product]
+
+**Business Game**: [Attention / Transaction / Productivity]
+
+### North Star Metric
+**Metric**: [precise name]
+**Definition**: [formula or measurement method]
+**Why this metric**: [explains value, leads revenue, is actionable]
+**Current value**: [if known]
+**Target**: [goal]
+
+### Validation
+| Criterion | Pass? | Notes |
+|----------|-------|-------|
+| Expresses value | [Y/N] | [explanation] |
+| Leading indicator | [Y/N] | [explanation] |
+| Measurable | [Y/N] | [explanation] |
+| Understandable | [Y/N] | [explanation] |
+| Actionable | [Y/N] | [explanation] |
+| Not vanity | [Y/N] | [explanation] |
+| Not gameable | [Y/N] | [explanation] |
+
+### Input Metrics
+| Input Metric | Drives North Star By | Owner | Current | Target |
+|-------------|---------------------|-------|---------|--------|
+
+### Metrics Constellation
+[Visual tree showing North Star → Input Metrics → Team Actions]
+
+### Counter-Metrics
+| Metric | Protects Against |
+|--------|-----------------|
+
+### Anti-Patterns Avoided
+[Why we didn't choose DAU, revenue, or other common but flawed metrics]
+```
+
+Save as markdown.
+
+### Step 6: Offer Next Steps
+
+- "Want me to **build a full metrics dashboard** around this?"
+- "Should I **create OKRs** based on these metrics?"
+- "Want me to **write SQL queries** to compute these metrics?"
+
+## Notes
+
+- The North Star should measure *value delivered*, not just *activity* — "daily active users" is only good if active use = value delivery
+- Revenue is never a good North Star — it's a lagging indicator that doesn't capture user value
+- Input metrics are what make the framework actionable — without them, the North Star is just a vanity dashboard
+- Revisit the North Star annually or when the business model changes significantly
+- Counter-metrics prevent Goodhart's Law — when a metric becomes a target, it ceases to be a good metric