Developer Platform Kickoff

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

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

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.

Instructions onlyAI & Agents
  1. 594cf70d343eCurrentcommit 594cf70Published Oct 8, 2026

Source and attribution

Source:samber/developer-platform-skillsinskills/developer-platform-kickoffat commit594cf70

License: MIT

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

Report or request removal