Sdk Portfolio Strategy

samber/developer-platform-skills/skills/sdk-portfolio-strategy

by samber594cf70d343eMIT3 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Decide a public API's language-SDK portfolio - which languages get official SDKs and in what order, generated vs handwritten build model, official and community support tiers with a promotion gate, SDK deprecation and end-of-life, and decoupling SDK SemVer from API versioning and release cadence. Use whenever the user mentions client libraries, SDKs, which languages to support first, an SDK generator (Stainless, Fern, OpenAPI Generator), community SDKs, or sunsetting an SDK - even if they never say "SDK portfolio". Portfolio strategy only, not single-SDK ergonomics or registry publishing. Do NOT use for whether to offer SDKs as a surface at all - use samber/developer-platform-skills@api-integration-surface-strategy instead.

  1. 594cf70d343eCurrentcommit 594cf70Published Oct 8, 2026

Source and attribution

Source:samber/developer-platform-skillsinskills/sdk-portfolio-strategyat commit594cf70

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal