atelier-typescript-api-design

Design REST APIs with consistent error handling and pagination.

39|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/martinffx/claude-code-atelier --skill atelier-typescript-api-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atelier-typescript-api-design
Source: https://github.com/martinffx/claude-code-atelier/tree/main/plugins/atelier-typescript/skills/atelier-typescript-api-design
Command: npx skills add https://github.com/martinffx/claude-code-atelier --skill atelier-typescript-api-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

REST API design patterns. Use when designing endpoints, error responses, pagination, versioning, or API structure. Framework-agnostic principles for building consistent, maintainable APIs.

Core Features & Use Cases

  • Guidelines for resource naming, versioning, error handling, and pagination.
  • Framework-agnostic patterns applicable across TypeScript backends and REST APIs.
  • Use Case: design a new API endpoint with consistent error shapes and pagination.

Quick Start

Start applying these REST API design patterns to your project by reviewing the reference guide and updating endpoints accordingly.

Frequently Asked Questions about atelier-typescript-api-design

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

FAQPage Schema
How do I design consistent REST API error handling in TypeScript?

REST API error handling uses RFC 7807 problem details to format predictable error responses. This pattern ensures consistent status codes and clear error shapes across all endpoints, making API failures maintainable and easy to debug.

What's the best way to implement cursor-based pagination for REST APIs?

Cursor-based pagination provides a reliable method to handle large datasets in REST APIs. Unlike offset pagination, cursors maintain stable result sets across data changes by using pointers to the last fetched item, preventing duplicate or missing records.

How do I structure REST API versioning and resource naming conventions?

REST API versioning uses versioned routes to manage endpoint changes without breaking existing clients. Resource naming follows framework-agnostic guidelines to ensure clear, consistent structure across projects and scalable services.

Do these REST API design patterns work with any TypeScript backend framework?

These REST API design patterns are framework-agnostic and apply across any TypeScript backend. They provide structural guidelines for endpoints, error formatting, and pagination without depending on specific libraries or platforms.

When should I use RFC 7807 problem details in my REST API?

RFC 7807 problem details should be used whenever your REST API returns errors. This standard format provides predictable error responses with consistent status codes, allowing clients to programmatically parse and handle API failures.

Why does REST API pagination break with standard offset limits?

Standard offset pagination breaks when underlying data changes between requests, causing duplicate or skipped records. Cursor-based pagination solves this by anchoring subsequent requests to a specific item rather than a numerical position.