api-integration
API Integration
Build robust, type-safe API clients from specs and documentation.
Key Principles
- Type everything — Runtime-validated types for all requests and responses
- Fail explicitly — No silent failures; throw typed errors with context
- Auth is first-class — Handle auth in the client layer, not scattered in calls
- Retry intelligently — Only idempotent methods, only transient failures, with backoff
- Isolate the boundary — Transform API shapes at the integration layer, not in app code
When NOT to Use
- Designing your own APIs — Use
api-designfor building endpoints others will consume - Writing API test suites — Use
testing-strategyfor test architecture, contract tests, mocking - Building SDKs for your API — Use
sdk-developmentfor packaging your own API as a client library
Quick Start Checklist
More from srstomp/pokayokay
architecture-review
Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.
299figma-plugin
Use when building Figma plugins, creating design automation tools, implementing sandbox/UI communication, or working with the Figma Plugin API for node manipulation, styles, and components.
79security-audit
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
48sdk-development
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).
28testing-strategy
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.
28session-review
Use after completing work sessions to analyze agent behavior patterns, prepare session handoffs for continuity, document completed work, identify blockers, or preserve context for the next session.
27