plugins/pokayokay/skills/sdk-development/SKILL.md
Use when building TypeScript SDKs, extracting shared code into packages, creating developer tooling libraries, designing clean API surfaces, or publishing to npm (public or private). Covers typed clients, error handling, multi-target bundling (ESM/CJS/browser).
npx skillsauth add srstomp/pokayokay sdk-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create professional TypeScript SDKs from scratch or by extraction.
| Reference | Description | |-----------|-------------| | extraction-scope-and-boundaries.md | Scope identification, dependency analysis, boundary definition | | extraction-usages-and-planning.md | Finding usages, test coverage, phased extraction plan | | package-structure-and-clients.md | SDK layout, client design patterns (single, modular, factory) | | configuration-and-api-design.md | Config interfaces, defaults, barrel exports, method signatures | | internal-architecture-and-best-practices.md | HTTP client, state management, tree-shaking, environment agnostic | | type-design.md | Strict types, branded types, generics, discriminated unions | | error-handling-and-async.md | Error class hierarchy, retry logic, request queues, token management | | events-storage-and-logging.md | Event emitter, storage abstraction, logger interface | | build-tools-and-output.md | tsup config, output formats, package.json exports, TypeScript config | | bundle-optimization-and-distribution.md | Bundle size, multi-platform builds, dual packages, monorepo | | publishing-and-registries.md | npm publishing, private registries, versioning, changelogs | | ci-cd-and-documentation.md | GitHub Actions, documentation, pre-publish checklist, deprecation |
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.