NestJS Backend Development Rules FAQs

Question 1

Is this skill compatible with Serverless and AWS Lambda?

Accepted Answer

Yes, it includes specific patterns for lazy-initialized Lambda handlers, @vendia/serverless-express integration, and esbuild configurations for optimized cloud deployment.

Question 2

Does it support environment variable validation?

Accepted Answer

Yes, it enforces the use of NestJS ConfigService for type-safe configuration access, which provides centralized validation and better testability than direct process.env access.

Question 3

Can I use this for GraphQL-based NestJS projects?

Accepted Answer

Absolutely. While it provides core NestJS rules, it is designed to be used alongside the nestjs-graphql skill for specialized resolver and schema patterns.

Question 4

Why does this skill use the --no-spec flag during generation?

Accepted Answer

The skill enforces a Test-Driven Development (TDD) approach where tests are written manually before implementation to match custom project structures, rather than relying on auto-generated CLI specs.

Question 5

How does this skill handle database schema changes?

Accepted Answer

It mandates the use of auto-generated TypeORM migrations via CLI to prevent drift between entity definitions and the actual database schema, prohibiting manual migration file edits.

NestJS Backend Development Rules

主要功能

使用场景

NestJS Backend Development Rules

主要功能

使用场景