From backend-nodejs
Use when scaffolding or reviewing Node.js project layout — NestJS module structure, Express project layout, monorepo with workspaces, ESM configuration, and tsconfig conventions
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-nodejs:nodejs-project-structureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
yourorg-order-service/
├── src/
│ ├── main.ts # Bootstrap
│ ├── app.module.ts # Root module
│ ├── order/
│ │ ├── order.module.ts # Feature module
│ │ ├── order.controller.ts
│ │ ├── order.controller.spec.ts
│ │ ├── order.service.ts
│ │ ├── order.service.spec.ts
│ │ ├── order.repository.ts
│ │ ├── dto/
│ │ │ ├── create-order.dto.ts
│ │ │ └── order-response.dto.ts
│ │ └── entities/
│ │ └── order.entity.ts
│ └── common/
│ ├── filters/
│ │ └── http-exception.filter.ts
│ └── pipes/
│ └── zod-validation.pipe.ts
├── test/
│ └── order.e2e-spec.ts
├── package.json
├── tsconfig.json
├── tsconfig.build.json
├── nest-cli.json
└── README.md
yourorg-order-service/
├── src/
│ ├── index.ts # Entry point
│ ├── app.ts # Express app setup
│ ├── routes/
│ │ └── order.routes.ts
│ ├── controllers/
│ │ └── order.controller.ts
│ ├── services/
│ │ └── order.service.ts
│ ├── middleware/
│ │ ├── error-handler.ts
│ │ └── validate.ts
│ └── types/
│ └── order.types.ts
├── tests/
│ ├── order.controller.test.ts
│ └── order.service.test.ts
├── package.json
├── tsconfig.json
└── README.md
yourorg-platform/
├── packages/
│ ├── api/ # NestJS API
│ ├── gateway/ # Express BFF
│ └── shared/ # Shared types/utils
├── package.json # workspaces: ["packages/*"]
├── tsconfig.base.json # Shared TS config
└── turbo.json # Turborepo config (optional)
"strict": true always"module": "NodeNext", "moduleResolution": "NodeNext""target": "ES2022" minimumtsconfig.base.json for shared settings in monoreposnpx claudepluginhub gagandeepp/software-agent-teams --plugin backend-nodejsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.