Backend api

Skill bg-szy/TOP-SKILLS/skills/marketplace/backend-api

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill backend-api

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and implement RESTful API endpoints following best practices for routing, versioning, and HTTP standards. Use this skill when creating or modifying API routes, controllers, or endpoints in files like routes/api.php, API controller files in app/Http/Controllers/Api/, controller files in app/Http/Controllers/, API resource classes, or when implementing REST API functionality. Use when working on URL structures, HTTP method handling (GET, POST, PUT, PATCH, DELETE), API versioning strategies, query parameter handling for filtering/sorting/pagination, HTTP status code responses, rate limiting configuration, or any API endpoint design decisions.

SKILL.md

2.0 KB, as published. Nobody here has run it

Backend API

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle backend API.

When to use this skill

When creating or editing API route definitions in routes/api.php or similar routing files
When building or modifying controllers in app/Http/Controllers/ or controller directories
When building or modifying API controllers in app/Http/Controllers/Api/ or API-specific controller directories
When implementing RESTful endpoints with proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
When designing URL structures and resource-based API paths
When implementing API versioning (URL path versioning like /api/v1/ or header-based versioning)
When configuring query parameters for filtering, sorting, pagination, or search functionality
When determining appropriate HTTP status codes for API responses (200, 201, 400, 404, 500, etc.)
When implementing rate limiting headers or API throttling
When creating nested resource routes or working with resource relationships in APIs
When writing API resource transformation classes or response formatting logic

Instructions