API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
These are the API design standards for our project. Apply these conventions whenever working with API endpoints.
/users, /orders, /products/order-items, /user-profiles/users/{id}/orders/orders?status=active&limit=20All API responses must follow this structure:
{
"data": {},
"error": null,
"meta": {
"page": 1,
"limit": 20,
"total": 100
}
}
data: 成功时返回的业务数据error: 错误时返回错误对象 { code, message, details }，成功时为 nullmeta: 分页和元信息，列表接口必须返回@public annotationAuthorization: Bearer <jwt-token>/api/v1/usersNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.
The English summary is being prepared. Showing the original description.
Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.
The English summary is being prepared. Showing the original description.
Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.
The English summary is being prepared. Showing the original description.
Perform a comprehensive code health check on a directory. Use when the user asks to analyze code quality, find issues, or get a health report.
The English summary is being prepared. Showing the original description.
Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.
The English summary is being prepared. Showing the original description.
Generate an interactive tree visualization of your codebase. Use when exploring a new repo or understanding project structure.
The English summary is being prepared. Showing the original description.