fec-api-integration
Installation
SKILL.md
API integration
Suitable for front-end and back-end boundary types, errors, authentication, uploads, real-time communication and user status design. Load integration-patterns.md when specific code patterns are required.
Purpose
Standardize front-end API integration boundaries to make requests, errors, authentication, and real-time data maintainable.
Procedure
- Clarify interface ownership
- For TypeScript full stack in the same team, tRPC or shared schema can be considered.
- Multi-language or multi-consumer API preferred OpenAPI/GraphQL codegen.
- Typed fetch wrapper can be used for small internal applications, but types must be maintained centrally.
- Do not scatter
fetch, URL, header, error parsing and token logic in components. - Public interfaces need to specify versions, compatibility windows, obsolete field policies, and caller scope.