Skip to content
Back to search

agent-nestjs-skills

I am back to NestJS, and have a few hours a week to get back to maintaining my few OSS repos. Sorry for the delay all!

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kadajett--agent-nestjs-skills/badge.svg)](/listings/kadajett--agent-nestjs-skills)

HTML

<a href="/listings/kadajett--agent-nestjs-skills"><img src="/api/listings/kadajett--agent-nestjs-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install this skill using [skills](https://github.com/vercel-labs/skills):

# GitHub shorthand
npx skills add Kadajett/agent-nestjs-skills

# Install globally (available across all projects)
npx skills add Kadajett/agent-nestjs-skills --global

# Install for specific agents
npx skills add Kadajett/agent-nestjs-skills -a claude-code -a cursor

Supported Agents

- Claude Code - OpenCode - Codex - Cursor - Antigravity - Roo Code

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 181 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # NestJS Best Practices
  2. ## I am back to NestJS, and have a few hours a week to get back to maintaining my few OSS repos. Sorry for the delay all!
  3. 📖 [For Humans <3](https://kadajett.github.io/agent-nestjs-skills/)
  4. A structured repository for creating and maintaining NestJS Best Practices optimized for agents and LLMs.
  5. ---
  6. <div align="center">
  7. <a href="https://semfora.ai">
  8. <img src="assets/semfora-logo.svg" alt="Semfora" width="380">
  9. </a>
  10. </div>
  11. > **From the maintainer:** I built this skill because agents write better NestJS when they can see real context. Context is also my day job: I founded [Semfora](https://semfora.ai), a semantic code analysis engine that hands coding agents call graphs, module maps, and change blast radius through nine MCP tools.
  12. >
  13. > Semfora launches on [Product Hunt on Tuesday, July 28](https://www.producthunt.com/products/semfora?launch=semfora). Support there on launch day means a lot.
  14. ---
  15. ## Installation
  16. Install this skill using [skills](https://github.com/vercel-labs/skills):
  17. ```bash
  18. # GitHub shorthand
  19. npx skills add Kadajett/agent-nestjs-skills
  20. # Install globally (available across all projects)
  21. npx skills add Kadajett/agent-nestjs-skills --global
  22. # Install for specific agents
  23. npx skills add Kadajett/agent-nestjs-skills -a claude-code -a cursor
  24. ```
  25. ### Supported Agents
  26. - Claude Code
  27. - OpenCode
  28. - Codex
  29. - Cursor
  30. - Antigravity
  31. - Roo Code
  32. ## Structure
  33. - `skills/nestjs-best-practices/` - The installable skill (this is what `skills add` copies into your project)
  34. - `SKILL.md` - Skill entry point and quick reference
  35. - `rules/` - Individual rule files (one per rule)
  36. - `_sections.md` - Section metadata (titles, impacts, descriptions)
  37. - `_template.md` - Template for creating new rules
  38. - `area-description.md` - Individual rule files
  39. - `scripts/` - Build scripts and utilities
  40. - `metadata.json` - Document metadata (version, organization, abstract)
  41. - __`AGENTS.md`__ - Compiled output (generated)
  42. ## Getting Started
  43. 1. Install dependencies:
  44. ```bash
  45. cd scripts && npm install
  46. ```
  47. 2. Build AGENTS.md from rules:
  48. ```bash
  49. npm run build
  50. # or
  51. ./scripts/build.sh
  52. ```
  53. ## Creating a New Rule
  54. 1. Copy `skills/nestjs-best-practices/rules/_template.md` to `skills/nestjs-best-practices/rules/area-description.md`
  55. 2. Choose the appropriate area prefix:
  56. - `arch-` for Architecture (Section 1)
  57. - `di-` for Dependency Injection (Section 2)
  58. - `error-` for Error Handling (Section 3)
  59. - `security-` for Security (Section 4)
  60. - `perf-` for Performance (Section 5)
  61. - `test-` for Testing (Section 6)
  62. - `db-` for Database & ORM (Section 7)
  63. - `api-` for API Design (Section 8)
  64. - `micro-` for Microservices (Section 9)
  65. - `devops-` for DevOps & Deployment (Section 10)
  66. 3. Fill in the frontmatter and content
  67. 4. Ensure you have clear examples with explanations
  68. 5. Run the build script to regenerate AGENTS.md
  69. ## Rule File Structure
  70. Each rule file should follow this structure:
  71. ```markdown
  72. ---
  73. title: Rule Title Here
  74. impact: MEDIUM
  75. impactDescription: Optional description
  76. tags: tag1, tag2, tag3
  77. ---
  78. ## Rule Title Here
  79. Brief explanation of the rule and why it matters.
  80. **Incorrect (description of what's wrong):**
  81. ```typescript
  82. // Bad code example
  83. ```
  84. **Correct (description of what's right):**
  85. ```typescript
  86. // Good code example
  87. ```
  88. Optional explanatory text after examples.
  89. Reference: [NestJS Documentation](https://docs.nestjs.com)
  90. ## File Naming Convention
  91. - Files starting with `_` are special (excluded from build)
  92. - Rule files: `area-description.md` (e.g., `arch-avoid-circular-deps.md`)
  93. - Section is automatically inferred from filename prefix
  94. - Rules are sorted alphabetically by title within each section
  95. - IDs (e.g., 1.1, 1.2) are auto-generated during build
  96. ## Impact Levels
  97. | Level | Description |
  98. |-------|-------------|
  99. | CRITICAL | Violations cause runtime errors, security vulnerabilities, or architectural breakdown |
  100. | HIGH | Significant impact on reliability, security, or maintainability |
  101. | MEDIUM-HIGH | Notable impact on quality and developer experience |
  102. | MEDIUM | Moderate impact on code quality and best practices |
  103. | LOW-MEDIUM | Minor improvements for consistency and maintainability |
  104. ## Scripts
  105. - `npm run build` (in scripts/) - Compile rules into AGENTS.md
  106. ## Contributing
  107. When adding or modifying rules:
  108. 1. Use the correct filename prefix for your section
  109. 2. Follow the `_template.md` structure
  110. 3. Include clear bad/good examples with explanations
  111. 4. Add appropriate tags
  112. 5. Run the build script to regenerate AGENTS.md
  113. 6. Rules are automatically sorted by title - no need to manage numbers!
  114. ## Documentation Website
  115. The documentation website source code lives on the [`docs` branch](https://github.com/Kadajett/agent-nestjs-skills/tree/docs/website). This separation keeps the skill installation lightweight while maintaining the full documentation site.
  116. To contribute to the website:
  117. ```bash
  118. git checkout docs
  119. cd website
  120. npm install
  121. npm run dev
  122. ```
  123. ## Acknowledgments
  124. - Inspired by the [Vercel React Best Practices](https://github.com/vercel-labs/agent-skills) skill structure
  125. - Compatible with [skills](https://github.com/vercel-labs/skills) for easy installation across coding agents
  126. ## Compatible Agents
  127. These NestJS skills work with:
  128. - [Claude Code](https://claude.ai/code) - Anthropic's official CLI
  129. - [AdaL](https://sylph.ai/adal) - Self-evolving AI coding agent with MCP support

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.