Menú
REST/GraphQL/tRPC API pattern library with validation, error handling, and documentation. Use when creating backend APIs.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | api-patterns |
| description | REST/GraphQL/tRPC API pattern library with validation, error handling, and documentation. Use when creating backend APIs. |
Identify API Type:
Detect Backend Framework:
Generate API Structure:
Add Best Practices:
CRUD Operations:
Filtering & Pagination:
Nested Resources:
Queries:
query GetUser($id: ID!) {
user(id: $id) {
id
name
posts {
title
}
}
}
Mutations:
mutation CreatePost($input: CreatePostInput!) {
createPost(input: $input) {
id
title
}
}
export const appRouter = router({
getUser: publicProcedure
.input(z.object({ id: z.string() }))
.query(async ({ input }) => {
return await db.user.findUnique({ where: { id: input.id } })
}),
})
const createUserSchema = z.object({
email: z.string().email(),
password: z.string().min(8),
name: z.string().min(2),
})
class CreateUser(BaseModel):
email: EmailStr
password: str = Field(min_length=8)
name: str = Field(min_length=2)
type CreateUserRequest struct {
Email string `json:"email" validate:"required,email"`
Password string `json:"password" validate:"required,min=8"`
Name string `json:"name" validate:"required,min=2"`
}
Standardized Error Responses:
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid input",
"details": [
{ "field": "email", "message": "Invalid email format" }
]
}
}
HTTP Status Codes:
Purpose: Backend API pattern library Used by: backend-generator agent, /api command
Comprehensive tech stack detection, framework identification, dependency analysis, and project.json generation. Use when analyzing project structure, detecting frameworks, identifying dependencies, discovering AI stack components, detecting databases, or when user mentions project detection, tech stack analysis, framework discovery, or project.json generation.
OpenAPI to Portman to Newman pipeline with auth injection for API contract testing. Use when building API tests from OpenAPI specs, injecting authentication into test collections, running contract tests, or when user mentions OpenAPI, Portman, API contract, Swagger, API testing pipeline, auth injection.
Run and analyze Newman (Postman CLI) tests. Use when running API tests, validating Postman collections, testing HTTP endpoints, or when user mentions Newman, Postman tests, API validation.
Health endpoint and critical path smoke testing patterns. Use when running quick validation tests, checking health endpoints, verifying critical paths respond correctly, or when user mentions smoke testing, health checks, quick validation, sanity checks.
Detection scripts and patterns for identifying test frameworks across all supported languages. Use when detecting test infrastructure, analyzing project testing setup, identifying coverage tools, or when user mentions test detection, framework identification, testing setup analysis.
Architecture design templates, mermaid diagrams, documentation patterns, and validation tools. Use when designing system architecture, creating architecture documentation, generating mermaid diagrams, documenting component relationships, designing data flows, planning deployments, creating API architectures, or when user mentions architecture diagrams, system design, mermaid, architecture documentation, or component design.