Back to search
agent-nestjs-skills
SkillGitHub
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
Markdown
[](/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)
- # NestJS Best Practices
- ## 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!
- 📖 [For Humans <3](https://kadajett.github.io/agent-nestjs-skills/)
- A structured repository for creating and maintaining NestJS Best Practices optimized for agents and LLMs.
- ---
- <div align="center">
- <a href="https://semfora.ai">
- <img src="assets/semfora-logo.svg" alt="Semfora" width="380">
- </a>
- </div>
- > **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.
- >
- > 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.
- ---
- ## Installation
- Install this skill using [skills](https://github.com/vercel-labs/skills):
- ```bash
- # 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
- ## Structure
- - `skills/nestjs-best-practices/` - The installable skill (this is what `skills add` copies into your project)
- - `SKILL.md` - Skill entry point and quick reference
- - `rules/` - Individual rule files (one per rule)
- - `_sections.md` - Section metadata (titles, impacts, descriptions)
- - `_template.md` - Template for creating new rules
- - `area-description.md` - Individual rule files
- - `scripts/` - Build scripts and utilities
- - `metadata.json` - Document metadata (version, organization, abstract)
- - __`AGENTS.md`__ - Compiled output (generated)
- ## Getting Started
- 1. Install dependencies:
- ```bash
- cd scripts && npm install
- ```
- 2. Build AGENTS.md from rules:
- ```bash
- npm run build
- # or
- ./scripts/build.sh
- ```
- ## Creating a New Rule
- 1. Copy `skills/nestjs-best-practices/rules/_template.md` to `skills/nestjs-best-practices/rules/area-description.md`
- 2. Choose the appropriate area prefix:
- - `arch-` for Architecture (Section 1)
- - `di-` for Dependency Injection (Section 2)
- - `error-` for Error Handling (Section 3)
- - `security-` for Security (Section 4)
- - `perf-` for Performance (Section 5)
- - `test-` for Testing (Section 6)
- - `db-` for Database & ORM (Section 7)
- - `api-` for API Design (Section 8)
- - `micro-` for Microservices (Section 9)
- - `devops-` for DevOps & Deployment (Section 10)
- 3. Fill in the frontmatter and content
- 4. Ensure you have clear examples with explanations
- 5. Run the build script to regenerate AGENTS.md
- ## Rule File Structure
- Each rule file should follow this structure:
- ```markdown
- ---
- title: Rule Title Here
- impact: MEDIUM
- impactDescription: Optional description
- tags: tag1, tag2, tag3
- ---
- ## Rule Title Here
- Brief explanation of the rule and why it matters.
- **Incorrect (description of what's wrong):**
- ```typescript
- // Bad code example
- ```
- **Correct (description of what's right):**
- ```typescript
- // Good code example
- ```
- Optional explanatory text after examples.
- Reference: [NestJS Documentation](https://docs.nestjs.com)
- ## File Naming Convention
- - Files starting with `_` are special (excluded from build)
- - Rule files: `area-description.md` (e.g., `arch-avoid-circular-deps.md`)
- - Section is automatically inferred from filename prefix
- - Rules are sorted alphabetically by title within each section
- - IDs (e.g., 1.1, 1.2) are auto-generated during build
- ## Impact Levels
- | Level | Description |
- |-------|-------------|
- | CRITICAL | Violations cause runtime errors, security vulnerabilities, or architectural breakdown |
- | HIGH | Significant impact on reliability, security, or maintainability |
- | MEDIUM-HIGH | Notable impact on quality and developer experience |
- | MEDIUM | Moderate impact on code quality and best practices |
- | LOW-MEDIUM | Minor improvements for consistency and maintainability |
- ## Scripts
- - `npm run build` (in scripts/) - Compile rules into AGENTS.md
- ## Contributing
- When adding or modifying rules:
- 1. Use the correct filename prefix for your section
- 2. Follow the `_template.md` structure
- 3. Include clear bad/good examples with explanations
- 4. Add appropriate tags
- 5. Run the build script to regenerate AGENTS.md
- 6. Rules are automatically sorted by title - no need to manage numbers!
- ## Documentation Website
- 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.
- To contribute to the website:
- ```bash
- git checkout docs
- cd website
- npm install
- npm run dev
- ```
- ## Acknowledgments
- - Inspired by the [Vercel React Best Practices](https://github.com/vercel-labs/agent-skills) skill structure
- - Compatible with [skills](https://github.com/vercel-labs/skills) for easy installation across coding agents
- ## Compatible Agents
- These NestJS skills work with:
- - [Claude Code](https://claude.ai/code) - Anthropic's official CLI
- - [AdaL](https://sylph.ai/adal) - Self-evolving AI coding agent with MCP support
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.