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 從公開儲存庫中收錄這些內容。

檢舉或申請下架