Global Validation FAQs

Question 1

How does this skill improve my development workflow?

Accepted Answer

It ensures architectural consistency by automating the use of standardized naming conventions and shared constants. By following established patterns for transaction-aware validation and error handling, it reduces bugs related to invalid data and duplicate records.

Question 2

When should I use this skill?

Accepted Answer

You should use this skill when adding decorators to DTOs, creating custom validation logic, implementing existence or uniqueness checks (like checkExist or checkExistTitle), or enforcing fail-fast validation logic at the start of application use cases.

Question 3

Does it support complex validation like database transactions?

Accepted Answer

Yes. The skill includes specific patterns for transaction-aware validation queries using Prisma. This allows Claude to perform existence and uniqueness checks within the same database transaction as the primary operation to prevent race conditions.

Question 4

What does the Global Validation skill do?

Accepted Answer

This skill provides Claude Code with specialized guidance for implementing comprehensive input validation and business rule enforcement. It utilizes class-validator decorators, custom validator services, and standardized patterns to ensure data integrity across your application.

Question 5

What specific validation patterns are included?

Accepted Answer

It covers DTO-based decorator validation, service-oriented validator classes, fail-fast patterns for use cases, custom sanitization decorators like IsNotEmptyString, and the integration of centralized validation constants for limit enforcement.

Global Validation

Global Validation

주요 기능

사용 사례

주요 기능

사용 사례