TypeScript Backend Rules FAQs

Question 1

Does it provide security guidelines?

Accepted Answer

Absolutely. It mandates input validation at the API boundary, parameterized queries to prevent SQL injection, and secure management of secrets via environment variables.

Question 2

Can it help prevent memory leaks in production?

Accepted Answer

Yes, it includes specific rules for memory management, such as proper cleanup of event listeners in service shutdown hooks and the use of WeakMaps for caching.

Question 3

How does it handle type safety?

Accepted Answer

The skill strictly prohibits the 'any' type, instead enforcing the use of 'unknown' combined with type guards, Zod validation, and modern TypeScript features like branded types and the 'satisfies' operator.

Question 4

Does this skill support frameworks other than NestJS?

Accepted Answer

While the skill features specific optimizations for NestJS and TypeORM, the core TypeScript principles, functional design patterns, and error handling strategies are applicable to any Node.js backend environment.

Question 5

What is the recommended approach for error handling?

Accepted Answer

It enforces a three-layered approach: mapping errors to status codes at the API layer, throwing domain-specific errors in the service layer, and handling connection-specific failures in the repository layer.

TypeScript Backend Rules

主要功能

使用场景

TypeScript Backend Rules

主要功能

使用场景