Image: NestJS
Why it mattersA coding agent that writes NestJS code can now load the framework's own rules first. The reader saves one round of fixing output.
NestJS opened a new repository on GitHub called nestjs/agent-skills on 20 November. The project carries official agent skills for the framework. The repository had 114 stars at the time of writing. The description is short: "Agent skills for Nest framework (node.js)."
NestJS is a Node.js framework for the server side. It is widely used. A coding agent like Claude Code, Codex or Cursor can now read this skill pack before writing NestJS code. The skills carry what the agent would otherwise have to guess from older training data.
What the skills try to fix
The README names three gaps. The first is that the agent's model is older than the current NestJS API. The second is that NestJS has its own first-party packages. The agent may not know which ones to pick. The third is a short list of real bugs. Each one passes a test and still reaches production.
The list of bugs is the useful part. The README names four, in plain words. A sign-in that leaks which emails exist. An optional-field marker that lets null through to a 500 error. A rate limiter that never sees the user. An event stream that keeps running after the owner revokes the key.
The six skills
The pack has six skills. Each covers one job inside a NestJS project.
nestjsfor creating a new project or changing the shape of one.nestjs-featurefor endpoints and input validation.nestjs-authfor sign-in and permissions.nestjs-datafor persistence.nestjs-testingfor writing and fixing tests.nestjs-productionfor getting an app ready to go live.
Only the skills a job needs are loaded by the agent. A task about a new endpoint pulls nestjs-feature. A task about a token leak pulls nestjs-auth.
Versions and setup
NestJS lists the versions the pack targets. The pack is tested on NestJS 12. It needs Node 20 or later. The README also records the exact package versions used in the tests. Two are @nestjs/authentication 0.1.6 and @nestjs/drizzle 0.0.2.
A team can install the pack for one project. The skills then travel in the repository, so every teammate's agent sees them. Or a team can install the pack globally on one machine. That version covers every project on that computer.
Why the format is open
The skills use the Agent Skills format. Claude Code, Codex and Cursor read that format. So do others. The pack is not locked to one vendor. A NestJS shop running two coding agents side by side gets the same output pattern from both.
For a team that builds a NestJS backend behind a coding agent, the useful move is small. Install the pack. Rerun the next feature. Read what changes about the generated code. Watch how often one of the four named bugs still shows up.
Source
- nestjs/agent-skills on GitHub, NestJS
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.

