$npx -y skills add ncklrs/startup-os-skills --skill platform-product-managerExpert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building deve
| 1 | # Platform Product Manager |
| 2 | |
| 3 | Strategic product management expertise for API-first and developer-focused platforms — from API design and developer experience to ecosystem building and platform metrics. |
| 4 | |
| 5 | ## Philosophy |
| 6 | |
| 7 | Great platform products aren't about features. They're about making developers **successful**. |
| 8 | |
| 9 | The best API and platform products: |
| 10 | 1. **Developer experience is product experience** — DX is your primary differentiator |
| 11 | 2. **APIs are user interfaces** — Design them with the same care as visual UIs |
| 12 | 3. **Documentation is product** — Great docs reduce support, increase adoption, drive success |
| 13 | 4. **Ecosystem multiplies value** — Your integrations make your platform stickier |
| 14 | |
| 15 | ## How This Skill Works |
| 16 | |
| 17 | When invoked, apply the guidelines in `rules/` organized by: |
| 18 | |
| 19 | - `api-*` — API design principles, standards, and patterns |
| 20 | - `dx-*` — Developer experience, onboarding, and success |
| 21 | - `docs-*` — Developer documentation strategy and standards |
| 22 | - `sdk-*` — SDK and library strategy |
| 23 | - `versioning-*` — API versioning, deprecation, and migration |
| 24 | - `community-*` — Developer community and ecosystem building |
| 25 | - `marketplace-*` — Integration marketplace and partner strategy |
| 26 | - `metrics-*` — Platform health and success metrics |
| 27 | |
| 28 | ## Core Frameworks |
| 29 | |
| 30 | ### Platform Maturity Model |
| 31 | |
| 32 | | Stage | Focus | Key Metrics | Team Structure | |
| 33 | |-------|-------|-------------|----------------| |
| 34 | | **Foundation** | Core API, basic docs | API uptime, error rates | PM + Engineers | |
| 35 | | **Growth** | DX, SDKs, onboarding | Time-to-first-call, activation | + DevRel, DX engineers | |
| 36 | | **Scale** | Ecosystem, marketplace | Integration count, partner revenue | + Partner team | |
| 37 | | **Platform** | Network effects, flywheel | Platform GMV, ecosystem value | Full platform org | |
| 38 | |
| 39 | ### The Developer Journey |
| 40 | |
| 41 | ``` |
| 42 | ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ |
| 43 | │ DISCOVER │ → │ EVALUATE │ → │ ADOPT │ → │ EXPAND │ |
| 44 | │ │ │ │ │ │ │ │ |
| 45 | │ - Search │ │ - Docs │ │ - Signup │ │ - More APIs │ |
| 46 | │ - Content │ │ - Sandbox │ │ - First call│ │ - Higher │ |
| 47 | │ - Referral │ │ - Pricing │ │ - Use case │ │ volume │ |
| 48 | │ │ │ │ │ solved │ │ - Referral │ |
| 49 | └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ |
| 50 | ``` |
| 51 | |
| 52 | ### API Design Hierarchy |
| 53 | |
| 54 | ``` |
| 55 | ┌─────────────────┐ |
| 56 | │ CONSISTENCY │ ← Predictable patterns |
| 57 | ├─────────────────┤ |
| 58 | │ SIMPLICITY │ ← Easy to understand |
| 59 | ├─────────────────┤ |
| 60 | │ DISCOVERABILITY│ ← Self-documenting |
| 61 | ├─────────────────┤ |
| 62 | │ RELIABILITY │ ← Stable and trustworthy |
| 63 | ├─────────────────┤ |
| 64 | │ PERFORMANCE │ ← Fast and efficient |
| 65 | └─────────────────┘ |
| 66 | ``` |
| 67 | |
| 68 | ### Developer Success Metrics Stack |
| 69 | |
| 70 | ``` |
| 71 | ┌─────────────────────────────────────────────────────────────────┐ |
| 72 | │ BUSINESS OUTCOMES │ |
| 73 | │ Revenue, Retention, Net Dollar Retention │ |
| 74 | ├─────────────────────────────────────────────────────────────────┤ |
| 75 | │ DEVELOPER SUCCESS │ |
| 76 | │ Active Developers, API Calls, Use Cases Completed │ |
| 77 | ├─────────────────────────────────────────────────────────────────┤ |
| 78 | │ DEVELOPER EXPERIENCE │ |
| 79 | │ Time-to-First-Call, Activation Rate, Support Tickets │ |
| 80 | ├─────────────────────────────────────────────────────────────────┤ |
| 81 | │ PLATFORM HEALTH │ |
| 82 | │ Uptime, Latency, Error Rates, Documentation Quality │ |
| 83 | └─────────────────────────────────────────────────────────────────┘ |
| 84 | ``` |
| 85 | |
| 86 | ## Platform Types |
| 87 | |
| 88 | | Type | Examples | Key Success Factor | Primary Metric | |
| 89 | |------|----------|-------------------|----------------| |
| 90 | | **Infrastructure API** | Stripe, Twilio, AWS | Reliability + DX | API calls, uptime | |
| 91 | | **Data API** | Plaid, Clearbit | Data quality + freshness | Data coverage | |
| 92 | | **Aggregation Platform** | Zapier, Segment | Integrations + ease | Connections made | |
| 93 | | **Developer Tools** | GitHub, Vercel | Workflow fit + speed | Active projects | |
| 94 | | **Embedded Platform** | Shopify Apps | Distribution + value | Install rate, GMV | |
| 95 | |
| 96 | ## API Style Comparison |
| 97 | |
| 98 | | Style | Best For | Complexity | Flexibility | Caching | |
| 99 | |-------|----------|--- |