competitive-cartographer
About
The Competitive Cartographer skill analyzes competitive landscapes to identify white space opportunities and provide positioning recommendations. Use it for competitive analysis, differentiation strategies, or "how to stand out" guidance across products, services, or portfolios. It focuses on strategic mapping and positioning, not market sizing or financial forecasting.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/competitive-cartographerCopy and paste this command in Claude Code to install this skill
Documentation
Competitive Cartographer
A strategic analyst who maps competitive spaces to reveal positioning opportunities, white space, and differentiation strategies. Creates "you are here" maps in crowded markets.
Quick Start
User: "How do I stand out as a senior frontend engineer?"
Cartographer:
1. Define space: "Professional portfolios for senior frontend engineers"
2. Identify players:
- Direct: Other senior frontend engineers in similar tech stacks
- Adjacent: Full-stack engineers, design engineers
- Aspirational: Apple's minimal aesthetic
3. Map on axes: Technical Depth (x) vs Design Polish (y)
4. Find white space: High tech + high design (rare combination)
5. Recommend positioning: "Engineer who thinks like a designer"
Key principle: Don't just list competitors - map them spatially to reveal positioning opportunities.
When to Use
Use when:
- User asks "how do I stand out?" or "what makes me different?"
- Launching product/service and need positioning strategy
- Feeling lost in crowded market
- Considering pivot or repositioning
Do NOT use when:
- User needs market size or TAM estimates
- Financial projections or fundraising strategy
- Specific feature-by-feature comparison
- User already has clear positioning
The 6-Step Process
| Step | Action |
|---|---|
| 1. Define Space | Domain, user's offer, background, goals |
| 2. Identify Players | Direct, adjacent, aspirational competitors |
| 3. Analyze Positioning | Extract taglines, visual strategy, content strategy |
| 4. Create Map | Plot on 2D axes, identify clusters |
| 5. Find White Space | Viable, defensible, sustainable, aligned gaps |
| 6. Recommend Strategy | Headline, differentiators, visual/content direction |
Common Anti-Patterns
Me-Too Positioning
| What it looks like | Why it's wrong |
|---|---|
| "We're like Airbnb but for X" | Invites comparison where you'll lose |
| Instead: Find unique angle that makes comparison irrelevant |
Swiss Army Knife Syndrome
| What it looks like | Why it's wrong |
|---|---|
| "We do everything for everyone" | In crowded markets, specialists beat generalists |
| Instead: Pick one thing you'll be known for |
Feature Parity Race
| What it looks like | Why it's wrong |
|---|---|
| "All competitor features plus one more" | Mature competitors will always out-feature you |
| Instead: Different approach/philosophy, not more features |
Ignoring Your Constraints
| What it looks like | Why it's wrong |
|---|---|
| Positioning as enterprise when solo founder | Can't deliver on promise, credibility destroyed |
| Instead: Position where constraints become advantages ("boutique", "founder-led") |
Types of White Space
| Type | Example |
|---|---|
| Intersection | "Technical depth + warm personality" (most pick one) |
| Under-served Audience | "Mid-market companies" (everyone targets enterprise or startups) |
| Contrarian | "Slow and thoughtful" (when everyone races to launch fast) |
Best Practices
Start with User, Not Market
- What's genuinely unique about user?
- What do they do better than anyone?
- What do they want to be known for?
- Then find where that fits in competitive landscape
Be Ruthlessly Honest
- Point out crowded positioning
- Identify genuine weaknesses
- Recommend against poor strategic fit
Provide Evidence
- "Here are 15 portfolios using exact same layout"
- "Here are 8 products with nearly identical taglines"
- "Here's how competitors cluster around this position"
Reference Files
| File | Contents |
|---|---|
references/mapping-process.md | Detailed 6-step methodology, TypeScript interfaces, axis pairs |
references/domain-positioning.md | Portfolio, SaaS, consulting-specific positioning + examples |
references/troubleshooting.md | Common issues, validation methods, best practices checklist |
Integration with Other Skills
| Skill | Integration |
|---|---|
| design-archivist | Visual pattern database informs differentiation strategy |
| vibe-matcher | Translate positioning into emotional/visual direction |
| career-biographer | Competitive context informs personal brand positioning |
Transform competitive chaos into strategic clarity.
GitHub Repository
Related Skills
copy
DesignThis Claude Skill provides expert copywriting for SaaS and startups, specializing in landing pages, product positioning, and conversion-focused messaging. It emphasizes using voice-of-customer research and strategic frameworks over intuition. Use it when you need to craft compelling marketing copy or develop a product's messaging strategy.
competitive-intelligence
OtherThis skill provides structured competitive analysis using Porter's Five Forces, SWOT, and positioning matrices. Use it to systematically evaluate market threats, opportunities, and strategic positioning against competitors. It generates detailed intelligence reports to inform strategic planning and decision-making.
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
creating-opencode-plugins
MetaThis skill provides the structure and API specifications for creating OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It offers implementation patterns for JavaScript/TypeScript modules that intercept and extend the AI assistant's lifecycle. Use it when you need to build event-driven plugins for monitoring, custom handling, or extending OpenCode's capabilities.
