Software Development
API Integration Surface Strategy
Decide which integration surfaces a platform offers external developers and AI agents - REST, GraphQL, gRPC, SQL access, bulk data sharing, webhooks, SDKs, CLI, MCP, embedded components - and in what build order, sequenced by reversal cost and audience rather than novelty. Use whenever the user mentions which API to build first, adding a GraphQL or MCP layer, an integration-surface roadmap, API-first vs embedded-first, or a missing surface blocking deals - even if they never say "integration surface". Umbrella strategy only - once a surface is chosen, per-surface design belongs to siblings such as samber/developer-platform-skills@webhook-platform-design and samber/developer-platform-skills@sdk-portfolio-strategy.
- Publisher / source
- samber/developer-platform-skills (found on skills.sh)
- Upstream record
- samber/developer-platform-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication
- Content fingerprint
f20abe51ef0208eafd4ab3ac0295d3174d2dbb14edaff5d0e1b764ae429afc1e