rest-conventions

Audit API endpoints for RESTful HTTP method and resource naming conventions.

13|2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/yanko-belov/code-craft --skill rest-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-conventions
Source: https://github.com/yanko-belov/code-craft/tree/main/skills/rest-conventions
Command: npx skills add https://github.com/yanko-belov/code-craft --skill rest-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RESTful API designs often violate HTTP semantics by using verbs in URLs or misusing HTTP methods, which leads to brittle integrations and poor caching behavior.

Core Features & Use Cases

  • Detect and correct REST anti-patterns such as verbs in URLs, POST for reads, and mutations using inappropriate methods.
  • Provide canonical patterns for CRUD operations, resource naming, and nested resources to create a consistent API surface.
  • Use Case: Audit an API surface and refactor endpoints to follow REST, improving clarity and evolvability.

Quick Start

Review your API endpoints and replace verbs in URLs with nouns, and ensure HTTP methods align with CRUD actions.

Frequently Asked Questions about rest-conventions

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

FAQPage Schema
Why should REST API endpoint URLs avoid using verbs and use nouns instead?

Using verbs in REST API URLs violates HTTP semantics and leads to brittle integrations and poor caching behavior. Naming endpoints with nouns ensures HTTP methods correctly define the resource operations.

How do I fix REST anti-patterns like using POST for read operations?

To fix REST anti-patterns like using POST for reads, audit your API surface and align HTTP methods with CRUD actions. Replace verbs in URLs with nouns to ensure proper resource operations and consistent design.

What are the canonical HTTP methods for CRUD operations in a RESTful API?

Canonical RESTful design maps HTTP methods to CRUD actions, ensuring GET retrieves, POST creates, PUT/PATCH updates, and DELETE removes resources. This alignment provides a consistent, semantic API surface.

How should I structure nested resources when designing a REST API?

Structuring nested resources in REST API design requires following canonical patterns for resource naming. This ensures a consistent API surface and clear hierarchical relationships between parent and child resources.

What are the limitations of refactoring endpoints to follow REST?

Refactoring endpoints to follow REST may require migrating existing integrations. While it improves clarity and evolvability, you must follow specific migration guidance to avoid breaking current clients during the transition.