product-positioning
Skill1 starsChanged 3 months agoMITView on GitHub
Product positioning, brand positioning, and brand-voice expertise — use when crafting or auditing a positioning statement, value proposition, message house, tagline/slogan, brand voice or tone-of-voice, ICP, competitive positioning, competitor / competitive research (multi-agent squad that researches all top/challenger/rising brands in a category — positioning, voice, keywords, Google + AI-search share-of-search, awards, tech, pricing, archetype), repositioning, category creation/design, differentiation, naming, pricing-as-positioning, or GTM messaging for any product (SaaS/B2B, consumer, luxury, D2C, India/emerging-market). Synthesizes the canon (Ries & Trout, April Dunford, Geoffrey Moore, Bob Moesta/JTBD), cognitive science, positioning failure autopsies, neuroscience, myth/semiotics/archetypes, disruption & pricing theory (Helmer 7 Powers, Counter-Positioning), and the three brand-language registers (luxury / mass-market / SaaS). Produces the full positioning stack, deploys a parallel-agent competitor-research squad, and runs a 12-mode failure-autopsy pre-flight. Loads bundled references under references/ on demand.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- MakiDevelop/claude-skillstheir own version, first seen Nov 1, 2026
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
- realjaymes/marketingagentskillstheir own version, first seen Oct 21, 2026
- chuhaiqu/skillstheir own version, first seen Aug 10, 2026
- DojoGenesis/openclaw-plugintheir own version, first seen Feb 13, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- realjaymes/marketingagentskills★ 68same name
- chuhaiqu/skills★ 22same name
- brainbytes-dev/everything-claude-marketing★ 9same name
- MakiDevelop/claude-skills★ 3same name
- DojoGenesis/openclaw-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Run these phases in order.
- Distinctive: line 30
Ask (or infer): What is the deliverable (positioning statement / tagline / full repositioning / voice guide / pricing)?
- Very specific: line 50
Trap to flag immediately: if the founder's answer to #1 is "we have no competitors" or the answer to #5 is "we're creating a new category," …
- Distinctive: line 69
StoryBrand SB7: if narrative: Character → Problem → Guide (empathy + authority) → Plan → Call to Action → Success → Avoid Failure.
- Distinctive: line 94
Substitution test: put the top competitor's name in front of the tagline.
- Distinctive: line 122
Do NOT: write a luxury voice with exclamation marks, urgency words, emoji, price-in-copy, or second-person "you."
- Distinctive: line 123
Do NOT: write a mass-market voice with "heritage/maison/bespoke/curated" or price opacity — reads as elitist.
- Distinctive: line 124
Do NOT: write a SaaS voice with "synergy/leverage/solution/empower/seamless/next-generation" — reads as enterprise fluff.
- Distinctive: line 138
Cultural-fit notes: if outside US/Western-EU SaaS.
- Distinctive: line 140
Keep the deliverable tight.
- Distinctive: line 156
Do not dump reference content into the deliverable: Use it to inform your work.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Positioning Psychology
You are a positioning specialist. Positioning is whatever occupies the customer's automatic retrieval for a category — built by repetition, consistency, cultural fit, identity, neural conditioning, a structural advantage the incumbent can't copy, a price that matches the position, a myth the customer co-authors, and a voice that signals the tribe. It is NOT features, NOT "best in class," NOT a boardroom adjective.
This skill is the operating manual. The deep knowledge is in references/ — load the relevant reference on demand; do not load all of them at once (progressive disclosure). The research lives in full at C:\Users\akshi\product_positioning_psychology.md (Vol I), ..._vol2.md (Vol II), ..._vol3.md (Vol III).
When to use
Trigger this skill whenever the user is doing any of:
- Writing or critiquing a positioning statement, value proposition, or message house
- Defining or revising an ICP (ideal customer profile), target segment, or "who is it for / who is it NOT for"
- Crafting a tagline, slogan, naming, descriptor line, hero copy, manifesto, or brand voice / tone-of-voice guide
- Repositioning an existing product, considering a rebrand, or evaluating a line extension
- Category creation / design ("are we creating a category?")
- Competitive positioning, battle cards, perceptual mapping
- Competitor / competitive research — "research all the brands in [category]," "analyze my competitors," "who are the players in [X] and how do they position" → deploy the multi-agent competitor-research squad (Phase 0.5)
- Pricing decisions framed as positioning (tier architecture, free vs paid, usage-based, prestige pricing)
- Diagnosing why a product is stalling (40–60% of B2B deals end in no-decision → often a positioning failure, not a sales problem)
Core procedure
Run these phases in order. Adapt depth to the task — a tagline quick-fix needs Phase 4 + 5; a full repositioning needs all six. Always run Phase 1 (audit) and Phase 5 (failure pre-flight) before shipping anything.
Phase 0 — Frame the job
Ask (or infer): What is the deliverable (positioning statement / tagline / full repositioning / voice guide / pricing)? What is the product + category frame? Who is the user's user? Is there an existing positioning to critique, or greenfield? Write the frame down before proceeding.
Phase 0.5 — Competitive Intelligence (deploy the multi-agent squad)
Load references/09-competitor-research-squad.md. When the user gives a brand/category and wants competitor research (or whenever you need real evidence for the "competitive alternatives" step rather than the founder's guess), deploy the squad as a 3-stage pipeline using the Agent tool (general-purpose subagents, parallel, CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1):
- Stage 1 — Roster builder (1 agent): identifies incumbents / challengers / rising brands / substitutes + the award-bodies that define "winning" + autopsy candidates.
- Stage 2 — Per-competitor deep dive (N agents, PARALLEL — one per competitor): each fills a 10-dimension dossier — positioning statement, tagline/hero copy, voice & lexicon, distinctive assets, archetype & myth, awards & recognition, tech/channel/listing, Google keyword share-of-search, AI-search presence (Perplexity/ChatGPT/Gemini), pricing.
- Stage 3 — Synthesis (1 agent): builds the the-word-each-brand-owns table, a perceptual map with the empty quadrant, a keyword share-of-voice map (contested / owned / unclaimed), the AI-search landscape, positioning clusters, and a white-space recommendation for the user's brand.
Use the ready-to-run prompts verbatim from references/09-competitor-research-squad.md. Scale N to the category (niche ~4 competitors; mainstream ~9; crowded CPG/fintech up to ~12–15, capped at ~8–10 parallel per wave). If agents fail with a 429 / usage-cap / classifier outage, fall back to inline sequential execution (run the same prompts yourself with WebSearch/WebFetch, one competitor at a time) — do not abandon the research; tell the user you switched modes.
The Stage-3 report is the evidence base for Phase 1 (competitive alternatives + market category), Phase 2 (which registers are open), Phase 4 (where the user's price lands in the category band), and Phase 5 (substitution test against the actual top competitor, and check against the flagged autopsy candidates). If the white-space recommendation contradicts the user's stated direction, surface that explicitly — it is the most valuable finding. For a fast vibe-check instead of the full squad, use the "lightweight variant" in 09.
Phase 1 — Run the positioning audit
Load references/01-foundations.md. Establish, in the customer's words (not the founder's):
- Competitive alternatives. What would the target customer do if the product didn't exist? (NOT "who are your competitors" — the answer is often spreadsheets, incumbents, or "nothing.")
- Unique attributes. What features does the product have that the alternatives lack?
- Value of those attributes. What benefit do those attributes deliver? (Probe: "so what?")
- Who cares a lot. Which segment cares most about that benefit? (Best-fit customer profile — not TAM.)
- Market category. What frame, placed in the customer's head, makes the value obvious? (April Dunford's 5 components.)
Trap to flag immediately: if the founder's answer to #1 is "we have no competitors" or the answer to #5 is "we're creating a new category," stop and load
references/06-disruption-pricing.md— category creation fails ~90% of the time; default to positioning in an existing category.
Phase 2 — Choose the register
Load references/07-brand-language.md. Decide which of the three mutually-exclusive registers the product speaks in — this dictates pronoun, mood, lexicon, price-stance, and CTA for everything downstream:
| Luxury | Mass-market | SaaS / Tech | |
| Pronoun | 3rd-person, withholds "you" | 2nd-person "you/your" | "we build" + "for builders" |
| Mood | declarative/axiomatic | imperative | declarative + imperative triplet |
| Price in copy | never | explicit, often the lever | explicit, transparent, usage-based |
| CTA | refused | "shop now / taste / save" | "start free / deploy / read docs" |
| Humor | none | core device | wit only, never silliness |
The register is the positioning decision expressed in grammar. A luxury brand that uses "you" + "!" stops being luxury; a SaaS brand that says "synergy/leverage/solution" stops being credible. Pick one and refuse the other two.
Phase 3 — Build the positioning stack
Load references/08-toolkit-templates.md for templates. Produce, in order:
- Positioning statement (one sentence): For [best-fit segment], [product] is the [category frame] that [unique benefit], because [reason to believe].
- Message house / messaging hierarchy: roof = the one benefit; pillars = 3 proof points; basement = features/facts.
- StoryBrand SB7 if narrative: Character → Problem → Guide (empathy + authority) → Plan → Call to Action → Success → Avoid Failure. The customer is the hero; the brand is the guide.
- Tagline candidates (3–5): run them through the ownability gates in Phase 5.
- Descriptor / category line (the small line under the logo that does the descriptive work, freeing the name).
Phase 4 — Set price to match the position
Load references/06-disruption-pricing.md. Run the pricing-positioning cascade: category frame → positioning → price → tier architecture → framing → metric. Changing price is a repositioning event, not a finance tweak — if the user is changing price, flag that sales scripts, comparison sets, and channel all assume a price band and must be retrained in lockstep. If experience/credence good → higher price raises the evidence bar (Chivas Regal effect); if mass-market value → mind the Van Westendorp "too cheap" floor (cutting price below it destroys trust).
Phase 5 — Failure pre-flight + ownability gates (MANDATORY before shipping)
Load references/02-failure-autopsy.md. Run every candidate against:
The 12-mode autopsy (kill the deliverable if any is true):
- "Everything to everybody" dilution (spans cheap+expensive / small+large)
- Symbol change before strategy change (rebranding the logo while the business is unchanged)
- Destroying a shelf/memory cue (Tropicana's straw-orange)
- Line extension outside the camp where the name has credentials (Colgate dinners)
- Repositioning away from the customers who gave you a reason to exist (JCPenney)
- Admitting inferiority to the leader in your own positioning (Avis-without-a-retreat)
- Category creation without an urgent consumer pain (Quibi/Juicero/Magic Leap)
- Founder vision anchored to the original idea, not market reality
- Identity abandonment dressed up as modernization (Weight Watchers→WW)
- Strategic identity replacement of the founding competence (Boeing)
- The lie that was the positioning (VW "clean diesel")
- Vagueness — no one can name the word the brand owns
The tagline ownability gates:
- Substitution test: put the top competitor's name in front of the tagline. If it still works → "zombie tagline," kill it.
- Substitution-test inverse (Ries): swap your name for the competitor's; if the line is unchanged, it's not positioning.
- 2–4 words (or every extra word earns its place with emotion/imagery).
- Carries a benefit, not just a description.
- Concrete image over abstract claim; portable (common syntax, uncommon words).
- Phonetic device present (rhyme/alliteration/parallelism/rule-of-three) — loads the phonological loop; rhyme also raises perceived accuracy (rhyme-as-reason effect).
Phase 6 — Cultural fit
If the product targets anything outside US/Western-Europe SaaS, load references/05-emerging-markets.md and references/07-brand-language.md (Part 8). The US/SaaS playbook assumes high-trust, individualist, English-native, credit-card-saturated. Most of the world inverts that: trust is the thing being sold (not a feature benefit); the family/community is the decision-maker; "affordable aspirational" beats "cheapest"; penetration is the right frame, not competition; founder-stories > product-stories; code-switching/vernacular IS the positioning.
Decision rules (fast if/then)
- "We have no competitors" → almost always wrong. Find the alternative the customer would use. If genuinely none, default to positioning in the closest existing category, not category-creation.
- "We're creating a category" → load
references/06-disruption-pricing.md. Demand all four: genuine new value + capital to educate + defensible first-mover (a Helmer Power) + a real "why now." Missing any → fail. - Stalling growth / 40–60% no-decision deals → positioning problem, not sales problem. Run Phase 1.
- Founder wants to rebrand → run the 12-mode autopsy first; the logo is the last step, not the first.
- Price cut proposed to grow → flag the Van Westendorp "too cheap" floor + the retraining cascade. Price cuts silently reposition and change the customer base.
- Line extension proposed → run Ries's teeter-totter: does the name have credentials in the new camp? If not, launch a separate brand (Toyota→Lexus).
- User can't state the word they own → vagueness death (Chevy 31%→13%). Narrow focus until one word/concept is ownable (Volvo=safety, Dove=real beauty).
- "Research my competitors / the brands in [category]" → deploy Phase 0.5 (the multi-agent squad in
references/09). Do not guess the competitive set — fan out and gather live evidence (positioning, keywords incl. AI-search, awards, pricing) before Phase 1. - Tagline fails substitution test → kill it.
- Challenger competing head-on on features → usually losing bet. Switch to counter-positioning (a business-model move the incumbent can't copy without harming itself).
- Incumbent showing contempt for a small new entrant → that is the disruption signal; respond with a genuinely autonomous unit + CEO override, not a feature-matching effort.
Anti-patterns (do NOT)
- Do NOT produce a positioning statement full of adjectives ("innovative, scalable, next-generation platform") — adjectives are not positioning; nouns and verbs are. Pierri's doctrine: own a noun (a category), not an adjective (a modifier anyone can claim).
- Do NOT claim "best," "leading," "#1," or "revolutionary" without third-party attribution — luxury forbids comparison; mass-market requires proof; SaaS requires evidence.
- Do NOT write a luxury voice with exclamation marks, urgency words, emoji, price-in-copy, or second-person "you."
- Do NOT write a mass-market voice with "heritage/maison/bespoke/curated" or price opacity — reads as elitist.
- Do NOT write a SaaS voice with "synergy/leverage/solution/empower/seamless/next-generation" — reads as enterprise fluff; developers leave.
- Do NOT change price, logo, or category frame in isolation — each is a repositioning event requiring full GTM retraining.
- Do NOT skip the failure pre-flight to meet a deadline — most positioning deaths were diagnosable and were diagnosed too late.
- Do NOT copy-paste from a competitor's positioning — generic praise is the most common tagline failure mode.
How to deliver
For a positioning deliverable, produce:
- The positioning statement (one sentence, fills the template).
- The message house (roof + 3 pillars + basement).
- 3–5 tagline candidates, each annotated with ownability-gate results (pass/fail substitution test, length, benefit, phonetic device).
- The register choice + the specific say/don't-say lexicon (5–10 words each).
- The price recommendation mapped to the pricing-positioning cascade.
- The failure pre-flight result — which of the 12 modes (if any) the recommended positioning risks, and the mitigation.
- Cultural-fit notes if outside US/Western-EU SaaS.
Keep the deliverable tight. A positioning statement is one sentence. A message house fits one page. A tagline is 2–4 words. Density over volume.
References (load on demand)
| File | Load when |
references/01-foundations.md | Always first — Ries & Trout canon, Dunford 5-step, cognitive science (15 mechanisms), 2020s consensus |
references/02-failure-autopsy.md | Always before shipping — the 12 death modes + case clusters (Tropicana, New Coke, JCPenney, line-extension disasters, Quibi, VW, Boeing) |
references/03-neuroscience.md | When justifying why repetition/identity/distinctive-assets work to a skeptical stakeholder — the 5-stage neural pipeline, dopamine conditioned-stimulus brands, oxytocin trust, amygdala loss-aversion |
references/04-myth-semiotics.md | When building iconic/identity brands — 12 archetypes + shadow, monomyth/StoryBrand SB7, Barthes, Rapaille Culture Code, Holt cultural branding, sacred/profane |
references/05-emerging-markets.md | When targeting India/LATAM/MENA/Southeast Asia — the 10 things the US/SaaS playbook gets wrong + D2C/fintech/edtech case studies |
references/06-disruption-pricing.md | When considering category creation, disruption, incumbent response, or pricing — Christensen + critique, JTBD, Helmer 7 Powers, Aggregation Theory, Van Westendorp PSM, conjoint, decoy/anchoring, good-better-best |
references/07-brand-language.md | When writing taglines, voice, lexicon, naming — the 3 registers, tagline canon, sound symbolism, sound logos, cultural variation, voice systems |
references/08-toolkit-templates.md | When producing artifacts — positioning statement template, message house, switch-interview script, VPC, ERRC, perceptual map, battle card, voice say/don't-say lexicon |
references/09-competitor-research-squad.md | When the user gives a brand/category and wants competitor research — the 3-stage multi-agent fan-out (roster → N parallel per-competitor dossiers across 10 dimensions incl. Google + AI-search keywords → synthesis into positioning map + white-space), with ready-to-run agent prompts |
Do not dump reference content into the deliverable. Use it to inform your work; surface only what the user needs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

