nestjs-patterns

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable patterns catalog with lean code examples, held back only by the absence of an explicit validation-gated workflow sequence.

Suggestions

Add a short end-to-end build/verify workflow (e.g., bootstrap → validate env → run tests → start) with an explicit validation checkpoint to lift workflow_clarity.

Include a concrete feedback loop for risky operations like transactions or env validation (e.g., fail boot and report missing vars) so error recovery is explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and pattern-focused: section headers, executable code blocks, and terse bullet rules, with no padding explaining what NestJS or basic TypeScript concepts are; every token earns its place.	3 / 3
Actionability	It provides multiple complete, copy-paste-ready examples (bootstrap, module/controller/service, DTO, guards, exception filter, test setup) plus concrete executable guidance, not pseudocode.	3 / 3
Workflow Clarity	Sections follow a sensible logical order (When to Activate → structure → bootstrap → production defaults), but there is no explicit sequenced multi-step workflow with validation checkpoints, and the testing section lacks a validate-fix-retry loop.	2 / 3
Progressive Disclosure	With no bundle files present, the skill is a single self-contained SKILL.md organized into clear, well-signaled sections with no nested references, which qualifies for a top score per the simple-skill guideline.	3 / 3
	Total	11 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, specific NestJS description with strong trigger terms and a clear niche, weakened only by the absence of an explicit "Use when..." trigger clause.

Suggestions

Add an explicit trigger clause such as 'Use when building or refactoring NestJS APIs, modules, controllers, providers, guards, or interceptors.' to fully answer the 'when' question.

Mention common user phrasings like 'NestJS services' or 'Nest modules' to broaden natural keyword coverage slightly.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete architectural elements ("modules, controllers, providers, DTO validation, guards, interceptors, config") plus the target ("production-grade TypeScript backends"), listing multiple specific actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does, but lacks any "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	It uses natural terms a user would actually say ("NestJS", "TypeScript backends", "controllers", "providers", "guards", "DTO validation", "interceptors") with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (NestJS-specific architecture) with distinct triggers unlikely to overlap with other skills' descriptions.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/nestjs-patterns/SKILL.md
Commit: 0c1d7be

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.