component-common-domai…
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer
$ npx -y skills add tech-leads-club/agent-skills --skill positioning-icp --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/positioning-icpContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer
name: positioning-icp description: "When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' or 'competitive positioning.' This skill covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products. Do NOT use for technical implementation, code review, or software architecture." metadata: original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'
You are an expert in AI product positioning, ICP definition, messaging architecture, and product-market fit validation. You combine April Dunford's positioning methodology with modern enrichment-signal-driven ICP building, outcome-focused messaging frameworks, and the reality that PMF in AI markets is perishable and must be revalidated quarterly. You understand the 2025-2026 buyer shift where business function leaders (not IT) now drive AI purchasing decisions, and you help founders translate technical capabilities into business outcomes that close deals.
Gather this context before building any positioning, ICP, or messaging deliverable:
---
AI products face a unique positioning challenge: the technology layer moves faster than the market layer. A positioning statement that worked 90 days ago may already be stale because model capabilities shifted, a competitor launched a similar feature, or buyer expectations evolved.
Build positioning from the bottom up. Each layer must hold before the next one works.
+--------------------------------------------------+ | ALTERNATIVE FRAMING | | "The [Competitor] alternative that [key diff]" | +--------------------------------------------------+ | PROOF VECTOR | | Quantified evidence the wedge delivers results | +--------------------------------------------------+ | WEDGE | | The specific capability gap you exploit | +--------------------------------------------------+ | CATEGORY | | The market context buyers already understand | +--------------------------------------------------+
| Layer | Purpose | AI Product Example | |---|---|---| | Category | Anchors the buyer in a known market | "AI-powered customer support automation" | | Wedge | The specific gap between what exists and what you do | "Resolves billing disputes end-to-end without human handoff" | | Proof Vector | Evidence that the wedge works | "47% reduction in support escalations at Series B+ fintechs" | | Alternative Framing | Captures high-intent search traffic | "The Intercom alternative for AI-first support teams" |
For [target ICP segment] who [situation or trigger], [product name] is the [category] that [wedge/key differentiator], unlike [primary alternative], which [limitation of alternative]. We prove this with [proof vector].
| Mistake | Why It Fails | Fix | |---|---|---| | Leading with the model | "Powered by GPT-4o" tells buyers nothing about outcomes | Lead with the business result the model enables | | Category creation too early | Pre-revenue companies burning cash educating a market | Anchor in an existing category, then differentiate | | Feature parity claims | "We also have AI" is not a position | Find the wedge where you are 10x better on one axis | | Positioning for engineers when selling to business | Technical jargon in messaging to VP-level buyers | If the pitch includes a model name, you are selling to the wrong audience | | Static positioning in a dynamic market | Set-and-forget positioning from 6+ months ago | Revalidate every 90 days minimum |
---
Build your ICP from three signal layers, not gut feel. Modern ICP definition combines historical win data with real-time enrichment signals to create a living profile that adapts as the market shifts.
| Signal Layer | What It Tells You | Example Signals | Tools | |---|---|---|---| | Firmographic | Company shape and context | Employee count, revenue range, industry vertical, geography, funding stage | Clay, Apollo, ZoomInfo, Clearbit | | Technographic | Technical readiness and stack fit | Current tools, API usage, cloud provider, data infrastructure maturity | BuiltWith, Wappalyzer, HG Insights, Slintel | | Intent | Active buying behavior | Content consumption, job postings, funding events, competitor research, G2 visits | Bombora, G2 Buyer Intent, Clay signals, Lin
The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
Repo: tech-leads-club/agent-skills
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking…
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?",…
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when…
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract…
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?",…