api-conventions

Standardize REST API endpoints, methods, and error handling across services.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/feraudet/ssii --skill api-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-conventions
Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/api-conventions
Command: npx skills add https://github.com/feraudet/ssii --skill api-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standards for REST API design across the project to ensure consistency in endpoints, responses, and error handling.

Core Features & Use Cases

  • Standardizes resource naming, HTTP methods, URL structures, and status codes for APIs like /api/consultants, /api/missions, and /api/dashboard
  • Provides a validation guide for request/response formats and error handling patterns
  • Supports onboarding and refactoring by ensuring uniform API design across services

Quick Start

When designing or updating REST endpoints, consult this guide to ensure consistent naming, methods, and error handling across the codebase.

Frequently Asked Questions about api-conventions

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

FAQPage Schema
How do I standardize REST API design across multiple services?

Standardize REST API design by applying centralized conventions for endpoint naming, HTTP methods, and error handling to ensure consistent request and response formats across backend services.

What HTTP status codes and error handling patterns should REST endpoints follow?

REST endpoints should follow explicit HTTP status code conventions and standardized error handling patterns to ensure uniform request/response formats and input validation across all API resources.

How do I validate request and response formats for REST APIs?

Validate request and response formats for REST APIs by applying centralized validation guides that enforce explicit input validation rules and consistent error handling patterns across services.

Can I use these REST conventions for onboarding and refactoring existing APIs?

Yes, these REST conventions support onboarding and refactoring by ensuring uniform API design across services, providing explicit endpoint naming and standardized HTTP methods for existing resources.

What's the best way to structure URL naming for resources like consultants and missions?

Structure URL naming by following explicit resource naming conventions for endpoints like /api/consultants and /api/missions, ensuring standardized REST API URL structures across the monorepo.