nodejs-backend
Skill3 starsChanged 6 months agoMITView on GitHub
Build production-ready Node.js backend APIs with Express, Prisma, Redis, and BullMQ. Use when creating REST APIs, database models, services, middleware, background jobs, or server-side logic.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- iliaal/ai-skillstheir own version, first seen Nov 7, 2026
- zeeshanalimughal/claude-skillstheir own version, first seen Oct 13, 2026
- alinaqi/claude-bootstraptheir own version, first seen Oct 8, 2026
- alinaqi/maggytheir own version, first seen Jun 12, 2026
- thesaifalitai/claude-setuptheir own version, first seen Feb 27, 2026
Used with
Projects with it also use security.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0xSeroSkillsecurity
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- iliaal/ai-skills★ 45same name
- thesaifalitai/claude-setup★ 9same name
- zeeshanalimughal/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- code-reviewSkill
- nestjs-backendSkill
- react-frontendSkill
- react-native-mobileSkill
- tddSkill
- Code Review & QualitySkill
- Data Transformation & AnalysisSkill
- deploySkill
- Incremental ImplementationSkill
- security-reviewSkill
- Test-Driven DevelopmentSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 139
Never hardcode secrets - use environment variables
- Distinctive: line 142
Use parameterized queries (Prisma handles this)
- Very specific: line 144
Use Helmet.js for HTTP security headers
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Node.js Backend Development
Build production-ready backend APIs following industry best practices.
Impact Levels
| Level | Description |
| CRITICAL | Must follow - security, data integrity |
| HIGH | Should follow - maintainability, performance |
| MEDIUM | Recommended - code quality |
Tech Stack
- Framework: Express.js + TypeScript
- ORM: Prisma
- Database: PostgreSQL
- Cache: Redis (ioredis)
- Queue: BullMQ
- Validation: Zod
- Logging: Pino
Project Structure
src/
├── config/ # Configuration (db, redis, env)
├── controllers/ # Route handlers (thin layer)
├── middleware/ # Auth, error handler, logging
├── repositories/ # Data access layer
├── routes/ # Route definitions
├── services/ # Business logic
├── utils/ # Helpers (AppError, logger)
└── index.ts # Entry pointPatterns
Layered Architecture (HIGH)
Request → Routes → Middleware → Controllers → Services → Repositories → DatabaseError Handling (CRITICAL)
// Use AppError for operational errors
class AppError extends Error {
constructor(
message: string,
public statusCode: number = 500,
public code: string = 'INTERNAL_ERROR'
) {
super(message);
this.name = 'AppError';
}
}
// Throw in services
if (!user) throw new AppError('User not found', 404, 'USER_NOT_FOUND');API Response Format
// Success
{ "success": true, "data": { ... } }
// Error
{ "success": false, "error": { "code": "...", "message": "..." } }
// Paginated
{ "success": true, "data": [...], "pagination": { "page": 1, "total": 100 } }Database (Prisma) (HIGH)
// Always use transactions for multi-step operations
await db.$transaction(async (tx) => {
const order = await tx.order.create({ data: orderData });
await tx.inventory.update({
where: { id: productId },
data: { stock: { decrement: 1 } }
});
return order;
});
// Select only needed fields
const user = await db.user.findUnique({
where: { id },
select: { id: true, email: true, name: true }
});Caching (Redis) (HIGH)
async function getOrSet<T>(
key: string,
fetcher: () => Promise<T>,
ttlSeconds = 3600
): Promise<T> {
const cached = await redis.get(key);
if (cached) return JSON.parse(cached);
const data = await fetcher();
await redis.setex(key, ttlSeconds, JSON.stringify(data));
return data;
}Queue (BullMQ) (MEDIUM)
// Producer
const emailQueue = new Queue('email', { connection: redis });
await emailQueue.add('send-welcome', { to: user.email, name: user.name });
// Consumer
const worker = new Worker('email', async (job) => {
await sendEmail(job.data);
}, { connection: redis });Security Rules (CRITICAL)
- Never hardcode secrets - use environment variables
- Hash passwords with bcrypt (12+ rounds)
- Validate all inputs with Zod
- Use parameterized queries (Prisma handles this)
- Implement rate limiting on auth endpoints
- Use Helmet.js for HTTP security headers
Testing (HIGH)
- 80% minimum test coverage
- Unit tests for services
- Integration tests for routes
- Use Vitest + Supertest
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
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.

