本文へ移動
cccskills
無料GitHub で公開

platform-product-manager

Expert 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 developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.

インストール方法を見る

含まれるファイル(13)

  • SKILL.md7.2 KB
  • rules/_sections.md1.2 KB
  • rules/api-design-principles.md5.5 KB
  • rules/api-security-authentication.md7.8 KB
  • rules/api-webhooks-events.md8.0 KB
  • rules/community-developer-relations.md6.8 KB
  • rules/docs-documentation-strategy.md6.5 KB
  • rules/dx-developer-onboarding.md5.9 KB
  • rules/dx-error-handling.md7.9 KB
  • rules/marketplace-integration-ecosystem.md6.9 KB
  • rules/metrics-platform-health.md8.2 KB
  • rules/sdk-library-strategy.md7.3 KB
  • rules/versioning-api-lifecycle.md6.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Platform Product Manager

Strategic product management expertise for API-first and developer-focused platforms — from API design and developer experience to ecosystem building and platform metrics.

Philosophy

Great platform products aren't about features. They're about making developers successful.

The best API and platform products:

  1. Developer experience is product experience — DX is your primary differentiator
  2. APIs are user interfaces — Design them with the same care as visual UIs
  3. Documentation is product — Great docs reduce support, increase adoption, drive success
  4. Ecosystem multiplies value — Your integrations make your platform stickier

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • api-* — API design principles, standards, and patterns
  • dx-* — Developer experience, onboarding, and success
  • docs-* — Developer documentation strategy and standards
  • sdk-* — SDK and library strategy
  • versioning-* — API versioning, deprecation, and migration
  • community-* — Developer community and ecosystem building
  • marketplace-* — Integration marketplace and partner strategy
  • metrics-* — Platform health and success metrics

Core Frameworks

Platform Maturity Model

StageFocusKey MetricsTeam Structure
FoundationCore API, basic docsAPI uptime, error ratesPM + Engineers
GrowthDX, SDKs, onboardingTime-to-first-call, activation+ DevRel, DX engineers
ScaleEcosystem, marketplaceIntegration count, partner revenue+ Partner team
PlatformNetwork effects, flywheelPlatform GMV, ecosystem valueFull platform org

The Developer Journey

┌─────────────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
│  DISCOVER   │ → │   EVALUATE  │ → │   ADOPT     │ → │   EXPAND    │
│             │   │             │   │             │   │             │
│ - Search    │   │ - Docs      │   │ - Signup    │   │ - More APIs │
│ - Content   │   │ - Sandbox   │   │ - First call│   │ - Higher    │
│ - Referral  │   │ - Pricing   │   │ - Use case  │   │   volume    │
│             │   │             │   │   solved    │   │ - Referral  │
└─────────────┘   └─────────────┘   └─────────────┘   └─────────────┘

API Design Hierarchy

                    ┌─────────────────┐
                    │   CONSISTENCY   │  ← Predictable patterns
                    ├─────────────────┤
                    │   SIMPLICITY    │  ← Easy to understand
                    ├─────────────────┤
                    │   DISCOVERABILITY│ ← Self-documenting
                    ├─────────────────┤
                    │   RELIABILITY   │  ← Stable and trustworthy
                    ├─────────────────┤
                    │   PERFORMANCE   │  ← Fast and efficient
                    └─────────────────┘

Developer Success Metrics Stack

┌─────────────────────────────────────────────────────────────────┐
│                    BUSINESS OUTCOMES                            │
│        Revenue, Retention, Net Dollar Retention                 │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER SUCCESS                            │
│     Active Developers, API Calls, Use Cases Completed           │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER EXPERIENCE                         │
│   Time-to-First-Call, Activation Rate, Support Tickets          │
├─────────────────────────────────────────────────────────────────┤
│                    PLATFORM HEALTH                              │
│        Uptime, Latency, Error Rates, Documentation Quality      │
└─────────────────────────────────────────────────────────────────┘

Platform Types

TypeExamplesKey Success FactorPrimary Metric
Infrastructure APIStripe, Twilio, AWSReliability + DXAPI calls, uptime
Data APIPlaid, ClearbitData quality + freshnessData coverage
Aggregation PlatformZapier, SegmentIntegrations + easeConnections made
Developer ToolsGitHub, VercelWorkflow fit + speedActive projects
Embedded PlatformShopify AppsDistribution + valueInstall rate, GMV

API Style Comparison

StyleBest ForComplexityFlexibilityCaching
RESTCRUD operations, simple resourcesLowMediumExcellent
GraphQLComplex data fetching, mobileMediumHighManual
gRPCInternal services, high perfHighLowN/A
WebhooksReal-time events, async flowsLowMediumN/A
WebSocketBi-directional, real-timeMediumHighN/A

Anti-Patterns

  • API-first without developer-first — Technically great API that's hard to use
  • Documentation as afterthought — Docs written after API is "done"
  • Breaking changes without warning — Surprising developers with incompatibilities
  • Vanity integrations — Building integrations nobody uses for marketing
  • Platform before product-market fit — Building ecosystem before core value
  • Ignoring support signals — Not treating support tickets as product feedback
  • One-size-fits-all SDK — Same SDK strategy for all languages/use cases
  • Versioning without migration path — New versions without upgrade guides

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

adr

無料

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

ncklrs のスキルをすべて見る

このスキルの問題を報告する