Api Integration Surface Strategy

samber/developer-platform-skills/skills/api-integration-surface-strategy

作者 samber594cf70d343eMIT3 个星标收录于 2026年10月8日更新于 2026年10月8日仓库10天前更新

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.

仅公开文件列表。将技能安装到工作区后即可查看文件内容。

路径大小类型
evals/evals.json22.5 KBapplication/json
references/build-order-case-studies.md4.8 KBtext/markdown
references/surface-condition-tables.md8.5 KBtext/markdown
SKILL.md17.1 KBtext/markdown

来源与署名

来源:samber/developer-platform-skills位于skills/api-integration-surface-strategy提交594cf70

许可证: MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架