NestJS API Standards
Response wrapping, pagination, and error standardization.
npx skills add majiayu000/claude-skill-registry --skill api-standards-hoangnguyen0403-agent-skills-standar --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# NestJS API Standards & Common Patterns ## **Priority: P1 (OPERATIONAL)** Standardized API response patterns and common NestJS conventions. ## Generic Response Wrapper - **Concept**: Standardize all successful API responses. - **Implementation**: Use `TransformInterceptor` to wrap data in `{ statusCode, data, meta }`. ## Pagination Standards (Pro) - **DTOs**: Use strict `PageOptionsDto` (page/take/order) and `PageDto<T>` (data/meta). - **Swagger Logic**: Generics require `ApiExtraModels` and schema path resolution. - **Reference**: See [Pagination Wrapper Implementation](references/pagination-wrapper.md) for the complete `ApiPaginatedResponse` decorator code. ## Custom Error Response - **Standard Error Object**: ```typescript export class ApiErrorResponse { @ApiProperty() statusCode: number; @ApiProperty() message: string; @ApiProperty() error: string; @ApiProperty() timestamp: string; @ApiProperty() path: string; } ``` - **Docs**: Apply `@ApiBadRequestResponse({ type: ApiErrorResponse })` globally or per controller.
- Priority: P1 (OPERATIONAL)
- Generic Response Wrapper
- Pagination Standards (Pro)
- Custom Error Response
What does the NestJS API Standards skill do?
Response wrapping, pagination, and error standardization.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-standards-hoangnguyen0403-agent-skills-standar --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.