Design Next.js App Router REST APIs with layered Route, Controller, Service, and Repository structure.
npx skills add https://github.com/Fivents/one-id --skill api-design-fivents
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/Fivents/one-id/tree/main/.claude/skills/api-design Command: npx skills add https://github.com/Fivents/one-id --skill api-design-fivents
This skill captures and enforces consistent API structure and best practices to prevent business logic sprawl, inconsistent error handling, and unvalidated inputs in Next.js App Router backends so teams deliver reliable, maintainable endpoints.
Design a Next.js App Router endpoint that follows Route → Controller → Service → Repository, uses DTOs and Zod for validation, returns standardized success and error responses, and keeps Prisma queries inside repositories.
High-intent search queries and answers about installing and using this skill.
Next.js App Router clean architecture separates Route, Controller, Service, and Repository layers to prevent business logic sprawl. This structure confines Prisma queries to repositories and standardizes API responses for maintainable endpoints.
Validating API inputs in Next.js requires defining DTOs and applying Zod validation. This approach reduces runtime errors by ensuring type safety and validating incoming payloads before they reach your business logic.
Prisma queries belong exclusively in the Repository layer of a clean architecture. Calling Prisma directly from controllers or route handlers is forbidden to ensure proper separation of concerns and simplify testing.
Standardizing REST API responses involves wrapping successful returns in a predictable { data } payload and mapping errors to consistent response formats. This ensures client applications receive stable and predictable API outputs.
Yes, using Zod and DTOs together enforces input safety in Next.js APIs. DTOs define data transfer structures while Zod validates runtime payloads, preventing unvalidated inputs from entering your service layer.
Business logic in route handlers indicates a missing clean architecture layer separation. Fix it by moving logic into Service classes and keeping route handlers strictly for HTTP request handling and controller delegation.
pounctBuild fullstack web applications with Next.js 16, TypeScript, Tailwind CSS 4, and Prisma ORM.
petbrainsGenerate REST endpoints and OpenAPI documentation from tRPC routers.
Dangerdan9631Create and manipulate domain models with Zod schemas and TypeScript.
naporin0624Create type-safe IPC routes with Hono and Zod validation.
