spine-api

Design contract-first REST or gRPC APIs with validation, authentication, and pagination.

69|8|Updated Mar 16, 2026

Search Tags:#design #api #validation #backend #pagination #auth #contract-first

Ready to run

npx skills add https://github.com/tonone-ai/tonone --skill spine-api

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spine-api
Source: https://github.com/tonone-ai/tonone/tree/main/team/spine/skills/spine-api
Command: npx skills add https://github.com/tonone-ai/tonone --skill spine-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and build contract-first APIs with strict validation, authentication, error handling, and scalable pagination to reduce rework and improve reliability.

Core Features & Use Cases

Contract-first design: define endpoints, data contracts, and error formats before implementation to ensure alignment across frontend, mobile, and services.
Auth and security: implement consistent authentication/authorization patterns and protect endpoints.
Robust pagination & error handling: standardize pagination (cursor or offset) and uniform error responses for client resilience.
Use Case: When asked to "build an API" for a feature, apply this skill to design the endpoint surface and contract before coding.

Quick Start

Draft a contract-first API schema and scaffold, then implement aligned endpoints and validation.

Frequently Asked Questions about spine-api

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

FAQPage Schema

What is contract-first API design and when should I use it?▼

Contract-first API design defines endpoints, data contracts, and error formats before implementation. Use it for REST or gRPC backend services to ensure alignment across web, mobile, and internal clients.

How do I build an API with consistent pagination and error handling?▼

To build an API with consistent pagination and error handling, standardize pagination using cursor or offset techniques and enforce uniform error response schemas to ensure client resilience across services.

What's the best way to implement authentication and authorization patterns across backend services?▼

The best way to implement authentication is by enforcing consistent authentication and authorization patterns during the API contract design phase, protecting endpoints and ensuring secure access across backend services.

Does contract-first API design work for both REST and gRPC services?▼

Contract-first API design works for both REST and gRPC backend services. It defines data contracts and enforces validation and secure access patterns across services for web and mobile clients.

How do I scaffold an API contract and implement aligned endpoints?▼

To scaffold an API contract and implement aligned endpoints, draft the contract-first API schema first. Then implement the endpoints and validation logic to match the predefined data contract exactly.

Why does my API integration break when error schemas are inconsistent?▼

API integrations break from inconsistent error schemas because clients cannot parse failures uniformly. Enforcing a strict contract-first design standardizes error formats and improves overall client resilience.