Developer Platform Kickoff

samber/developer-platform-skills/skills/developer-platform-kickoff

作者 samber594cf70d343eMIT3 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新

Before starting any developer-platform, public-API, or integration work - or whenever no other platform skill has been chosen - route the task to the right skill in samber/developer-platform-skills, or say plainly that none fits, then bootstrap or resume the project's shared platform context. Fires at every API or platform project start, at each recurring platform review, and whenever routing is unclear. Use whenever the user mentions a developer platform kickoff, a new public API program, an integration-surface roadmap, "which platform skill do I need", "where do I start with our public API", platform skill routing, or a recurring platform check-in - even if they never name a skill or ask to be routed. It spans REST, GraphQL and gRPC design, webhooks, SDKs, MCP, OAuth and API keys, rate limits, versioning, developer portals, docs, sandboxes, marketplaces, and partner strategy, so an ambiguous platform question belongs here first. Outputs a short-list and an ordered skill chain, never the design itself.

僅含說明AI & Agents
  1. 594cf70d343e目前提交 594cf70發布於 2026年10月8日

來源與署名

來源:samber/developer-platform-skills位於skills/developer-platform-kickoff提交594cf70

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架