api-design

Design REST APIs for finance applications with JWT authentication and OpenAPI documentation.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/ms-moar/ccc-media --skill api-design-ms-moar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design
Source: https://github.com/ms-moar/ccc-media/tree/main/ailabspro/files/extracted/v31-resources/cursor-context-in-claude/.claude/skills/api-design
Command: npx skills add https://github.com/ms-moar/ccc-media --skill api-design-ms-moar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a consistent, secure, production-ready blueprint for designing, implementing, and reviewing REST APIs for financial applications, reducing common mistakes around money handling, authentication, validation, and error handling.

Core Features & Use Cases

  • Resource mapping & endpoints: Standard patterns for accounts, transactions, budgets, categories, and reporting with RESTful routes and versioning.
  • Security & auth: JWT bearer authentication patterns and middleware guidance to ensure per-user access controls.
  • Validation & errors: Zod/Joi validation schemas, structured error responses, and AppError patterns for clear client feedback.
  • Operational concerns: Pagination (page and cursor), rate limiting, request IDs, soft deletes, and money-in-cents handling to avoid floating point issues.
  • Documentation: OpenAPI templates and examples to generate accurate Swagger specs and client integrations.

Quick Start

Design a versioned REST API for accounts, transactions, and budgets using JWT authentication, Zod validation, pagination, standardized error responses, and an OpenAPI spec.

Frequently Asked Questions about api-design

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

FAQPage Schema
How do I design a REST API for finance applications that handles money safely?

Design REST APIs for finance applications by mapping business entities to secure HTTP endpoints, using money-in-cents handling to avoid floating point issues, and applying standardized error responses. This ensures accurate transaction processing and robust data integrity.

What's the best way to implement JWT bearer authentication for a financial REST API?

Implement JWT bearer authentication for financial REST APIs using dedicated middleware patterns to enforce per-user access controls. This approach secures account and transaction endpoints by validating tokens before processing requests.

How do I validate requests and standardize error responses in a finance API?

Validate requests in finance APIs using Zod or Joi validation schemas to check input data. Standardize error responses using structured formats and AppError patterns to provide clear, consistent client feedback during CRUD operations.

How do I generate OpenAPI documentation for a versioned REST API with pagination?

Generate OpenAPI documentation for versioned REST APIs using built-in templates and examples that map pagination and filtering parameters. This produces accurate Swagger specs for client integrations across accounts, budgets, and reporting endpoints.

Can I use cursor-based pagination and rate limiting for high-volume transaction endpoints?

Yes, you can apply both cursor and page-based pagination alongside rate limiting for transaction endpoints. These operational concerns manage data load and protect finance APIs from excessive requests during heavy reporting or CRUD operations.