NestJS API Dev

Develop NestJS APIs following Sellernote's 3-layer architecture and convention documents.

Convention Loading

Before starting any work, Read the relevant reference files from references/ within this skill directory:

1. Always read first (core rules):

   • references/BACKEND_CONVENTION.md - 3-layer architecture, DTO/Entity naming, test strategy, anti-patterns
   • references/BACKEND_ARCHITECTURE_CONVENTION.md - Layer responsibility matrix, forbidden patterns, monorepo dependency rules (Application → Library)
   • references/NESTJS_CONVENTION.md - NestJS-specific rules: project structure, DI, decorators, money handling, module config, controller/service/repository splitting, Guard/Interceptor/Pipe roles, exception handling

2. Read when relevant:

   • references/API_SPEC_CONVENTION.md - When designing endpoints: RESTful URL design, response formats, pagination, filtering/sorting, bulk ops, async processing (202 Accepted), file upload, idempotency, caching, rate limiting, OpenAPI/Swagger, full @SellernoteApi* decorator reference
   • references/SECURITY_CONVENTION.md - When implementing auth (JWT with Refresh Token Rotation, RBAC), input validation (SQL injection, XSS, Mass Assignment, Path Traversal), transport security (HTTPS, CORS, security headers, cookie security), sensitive data management, PII handling, security logging/auditing
   • references/COMMON_CONVENTION.md - When unsure about naming conventions, domain glossary, git/branch/commit conventions, error code format, logging levels/format
   • references/TYPESCRIPT_CONVENTION.md - When unsure about TS style, import ordering, enum vs union/as const, type-only imports, linter/formatter config