tdg-personal/nestjs-patterns
NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.
71
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
64%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at listing specific NestJS capabilities and uses natural trigger terms that developers would search for. However, it critically lacks any 'Use when...' guidance, which means Claude has no explicit signal for when to select this skill over others. Adding trigger conditions would significantly improve its effectiveness in a multi-skill selection scenario.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about NestJS, building TypeScript APIs with Nest, or mentions decorators, dependency injection, guards, or interceptors in a Node.js backend context.'
Consider adding file extension or project indicator triggers like 'nest-cli.json', '.module.ts', or '@nestjs/' imports to help Claude identify NestJS projects.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete concepts: modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends. These are concrete architectural components rather than vague abstractions. | 3 / 3 |
Completeness | Describes 'what' (NestJS architecture patterns for various components) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'NestJS', 'modules', 'controllers', 'providers', 'DTO validation', 'guards', 'interceptors', 'config', 'TypeScript backends'. These cover the main terms a developer working with NestJS would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | NestJS is a specific framework with distinct terminology (guards, interceptors, providers, DTO validation). This is clearly distinguishable from general TypeScript, Express, or other backend framework skills, making conflict unlikely. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable NestJS reference with executable code examples covering the major framework concerns. Its main weaknesses are the lack of workflow sequencing (no step-by-step guidance for common multi-step tasks like scaffolding a new feature module end-to-end) and some verbosity in stating patterns Claude already knows. The content would benefit from progressive disclosure via linked sub-files for deeper topics.
Suggestions
Add a sequenced workflow for a common multi-step task (e.g., 'Adding a new feature module: 1. Generate module → 2. Define DTOs → 3. Implement service → 4. Wire controller → 5. Validate with tests') with explicit checkpoints.
Move detailed sections like exception filters, auth/guards, and testing into separate referenced files (e.g., 'See [AUTH.md](AUTH.md) for guard and strategy patterns') to improve progressive disclosure.
Remove obvious best-practice bullets that Claude already knows (e.g., 'Put business logic in services, not controllers') to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some guidance Claude already knows (e.g., 'Put business logic in injectable services, not controllers', 'Controllers should stay thin'). The bullet-point tips after each section add some value but several state obvious NestJS best practices that Claude would already understand. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready TypeScript code for bootstrap, modules, controllers, services, DTOs, guards, exception filters, config, and testing. Each section has concrete, runnable examples with specific decorators, pipes, and patterns. | 3 / 3 |
Workflow Clarity | The skill covers many NestJS concerns but presents them as independent patterns rather than a sequenced workflow. There are no explicit validation checkpoints or feedback loops for multi-step processes like setting up a new module or adding auth. The testing section lacks a verify-then-fix cycle. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but everything is inline in a single file with no references to external files for deeper topics like auth strategies, Prisma integration, or advanced testing patterns. For a skill this comprehensive, splitting detailed examples into referenced files would improve navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents