backend-api
遵循路由、版本控制和HTTP标准的最佳实践设计和实现RESTful API端点。在创建或修改API路由、控制器或端点(如routes/api.php中的文件、app/Http/Controllers/Api/中的API控制器文件、app/Http/Controllers/中的控制器文件、API资源类)或实现REST API功能时使用此技能。在处理URL结构、HTTP方法处理(GET、POST、PUT、PATCH、DELETE)、API版本控制策略、过滤/排序/分页的查询参数处理、HTTP状态码响应、速率限制配置或任何API端点设计决策时使用。
📖 中文导读:遵循路由、版本控制和HTTP标准的最佳实践设计和实现RESTful API端点。在创建或修改API路由、控制器或端点(如routes/api.php中的文件、app/Http/Controllers/Api/中的API控制器文件、app/Http/Controllers/中的控制器文件、API资源类)或实现REST API功能时使用此技能。在处理URL结构、HTTP方法处理(GET、POST、PUT、PATCH、DELETE)、API版本控制策略、过滤/排序/分页的查询参数处理、HTTP状态码响应、速率限制配置或任何API端点设计决策时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: Backend API description: 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.
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.phpor 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
For details, refer to the information provided in this file: backend API