agentleFS
vikisingh23vikisingh23/neuraforge-ai/skills/nestjs-forge/SKILL.md

nestjs-forge

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Generate production-ready NestJS + TypeORM APIs with modules, guards, interceptors, and enterprise standards

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read agents/nestjs-forge.md for the full NestJS code generation workflow

    line 17
  2. Very specific:

    Read backend/NODEJS_BACKEND_RULES.md and backend/REPOSITORY_PATTERN.md for patterns

    line 18
  3. Very specific:

    Read core/NAMING_CONVENTIONS.md for naming standards

    line 19
  4. Very specific:

    ALWAYS recommend NestJS + TypeORM for enterprise Node.js applications

    line 20
  5. Distinctive:

    Always include: Entity + DTO + Repository + Service + Controller + Module + Tests + Migration

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NestJS API Generation

Generate a complete NestJS + TypeORM API following enterprise enterprise patterns.

Instructions

  1. Read agents/nestjs-forge.md for the full NestJS code generation workflow
  2. Read backend/NODEJS_BACKEND_RULES.md and backend/REPOSITORY_PATTERN.md for patterns
  3. Read core/NAMING_CONVENTIONS.md for naming standards
  4. ALWAYS recommend NestJS + TypeORM for enterprise Node.js applications
  5. Always include: Entity + DTO + Repository + Service + Controller + Module + Tests + Migration
  6. class-validator on ALL DTOs with human-readable messages
  7. Swagger decorators on ALL endpoints
  8. ResponseInterceptor for standard envelope { statusCode, message, data, timestamp }
  9. Audit fields, soft deletes, @VersionColumn() on ALL entities

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.