Delegate independent tasks to specialized agents working concurrently with isolated context.
Competitive Cartographer
competitive-cartographer
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations. Use when users need competitive analysis, market positioning
SKILL.md
Full skill instructions
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.
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
