api-implementer
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Design and implement backend APIs following RESTful principles, consistent naming conventions, and API best practices. Use this skill when working on any backend API code including endpoints, routes, controllers, request handlers, response formatters, authentication mechanisms, API middleware, versioning strategies, or API documentation. Use when creating new API features, refactoring existing API code, implementing REST resources, designing API architecture, setting up API configuration, or working with any files in API-related directories (routes/, controllers/, api/, handlers/, middleware/). Use when working with Express.js, NestJS, FastAPI, Django REST Framework, Rails API, Spring Boot REST, or any other backend API framework.
Génère des Next.js Server Actions comme couche d'orchestration mince entre frontend et backend NestJS. À utiliser lors de la création d'actions, mutations, ou quand l'utilisateur mentionne "server action", "mutation", "form action", "useTransition", "revalidatePath".
Expert code writer specializing in production-grade Python, FastAPI, and microservices development. Activated for writing clean, maintainable, well-tested code following best practices for the SaaS platform.
Guide for runtime validation with Zod in TypeScript. Covers schema design patterns, type inference, composition, error handling, and common patterns for domain modeling.
REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs
REST API implementation patterns. Use when building HTTP APIs.
This skill should be used when the user asks to "create a Next.js page", "add a route", "create a layout", "implement server components", "add client components", "create API routes", "implement server actions", "add loading states", "handle errors in Next.js", "create dynamic routes", "implement parallel routes", "add intercepting routes", or mentions Next.js App Router, React Server Components (RSC), or app directory patterns.
WHEN: GraphQL schema review, resolver patterns, N+1 detection, query complexity, API security WHAT: Schema design + N+1 detection + Query complexity + Input validation + Error handling + DataLoader patterns WHEN NOT: REST API → api-documenter, Database schema → schema-reviewer, ORM → orm-reviewer
REST API design principles, conventions, and patterns. Use when: designing APIs, choosing status codes, error handling, caching, auth patterns. Do not use for: framework-specific implementation (use fastapi, axum skills). Workflow: This skill (design) → fastapi/axum (implementation).
Manages User Service operations including Prisma schema, migrations, authentication logic, and profile management. Use when working on user-related backend features.
HTTP actions for webhooks and API endpoints in Convex. Use when building webhook handlers (Stripe, Clerk, GitHub), creating REST API endpoints, handling file uploads/downloads, or implementing CORS for browser requests.
백엔드 API 계약(DTO, 에러 응답) 변경 시 반드시 사용. 프론트엔드 타입과 에러 처리가 백엔드와 일치하는지 확인. app/backend/**/dto/ 또는 **/exception/ 파일 수정 후 이 skill을 자동 적용.
Generates a Laravel FormRequest class for validation. Use when creating or updating data (e.g., "Add validation for student registration").
Organization-wide REST/GraphQL API conventions: URL and naming rules, versioning, pagination/filtering, status codes, authentication headers, and compatibility guidance
REST API design patterns, authentication, and error handling for this SaaS application
Prevent leaking database errors and P-codes to clients. Use when implementing API error handling or user-facing error messages.
Backend patterns for Convex queries, mutations, and Clerk authentication integration
ALWAYS USE when working with Pydantic models, BaseModel, Field, validators, or data contracts. MUST be loaded before creating any Pydantic schemas, configuration classes, or API contracts. Provides v2 syntax validation and SDK research steps.
BoxLogのtRPC v11ルーターを作成。サービス層分離、Zodバリデーション、エラーハンドリングを適用。
Auto-generate Pydantic models from schema descriptions with type hints, validation rules, examples, and JSON schema export. 75% token savings (2,000→500).