sdk-boundary

Enforces frontend-backend separation by auditing TypeScript projects for raw HTTP calls and requiring OpenAPI-generated SDKs.

6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/markacianfrani/armor --skill sdk-boundary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdk-boundary
Source: https://github.com/markacianfrani/armor/tree/main/skills/sdk-boundary
Command: npx skills add https://github.com/markacianfrani/armor --skill sdk-boundary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @hey-api/openapi-ts.

What problem does it solve?

This Skill prevents frontend-backend drift by enforcing a strict contract where the frontend communicates with the backend exclusively through a generated, type-safe SDK.

Core Features & Use Cases

  • Contract Enforcement: Eliminates raw HTTP calls like fetch or axios in favor of generated SDK functions.
  • Type Safety: Ensures backend schema changes propagate as TypeScript errors, preventing silent runtime failures.
  • Use Case: When auditing a frontend codebase, use this skill to identify and replace scattered, manual API calls with a centralized, autogenerated SDK client.

Quick Start

Use the sdk-boundary skill to audit the current project for raw fetch usage and generate the required SDK configuration.

Frequently Asked Questions about sdk-boundary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce type safety between a TypeScript frontend and a backend API?

You can enforce type safety by generating a type-safe SDK from an OpenAPI specification and requiring the frontend to communicate exclusively through those generated functions. This prevents silent runtime failures by surfacing backend schema changes as TypeScript errors.

What is the best way to stop using raw fetch calls in a frontend codebase?

The best way to eliminate raw fetch calls is to audit the codebase for manual HTTP requests and replace them with a centralized, autogenerated SDK client. This enforces a strict architectural boundary and ensures contract consistency across API integrations.

Do I need an OpenAPI specification to generate a type-safe SDK?

Yes, a valid OpenAPI specification is required to generate a type-safe SDK. You also need a configured code generator to maintain synchronization between the API definitions and the client-side TypeScript implementations.

How does OpenAPI codegen prevent frontend-backend contract drift?

OpenAPI codegen prevents frontend-backend contract drift by enforcing a strict boundary where the frontend uses generated SDK functions instead of raw HTTP calls. Any backend schema changes automatically propagate as TypeScript compile-time errors.

Can I use this approach to audit existing TypeScript API integrations?

Yes, you can audit an existing TypeScript frontend codebase to identify scattered manual API calls. The audit process replaces raw fetch or axios usage with a centralized, autogenerated SDK client to ensure strict type safety.