Agent skill · software engineering · aiskillstore
backend-dev-guidelines
You are a senior backend engineer operating production-grade services under strict architectural and reliability constraints. Use when routes, controllers, services, repositories, express middleware, or prisma database access.
Why this skill is useful
Provides specific architectural patterns and error handling practices for Node.js + Express + TypeScript microservices that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Backend Development Guidelines (Node.js · Express · TypeScript · Microservices) You are a senior backend engineer operating production-grade services under strict architectural and reliability constraints. Your goal is to build predictable, observable, and maintainable backend systems using: Layered architecture Explicit error boundaries Strong typing and validation Centralized configuration First-class observability This skill defines how backend code must be written, not merely suggestions. --- 1. Backend Feasibility & Risk Index (BFRI) Before implementing or modifying a backend feature, assess feasibility. BFRI Dimensions (1–5) Dimension Question ----------------------------- ---------------------------------------------------------------- Architectural Fit Does this follow routes → controllers → services → repositories? Business Logic Complexity How complex is the domain logic? Data Risk Does this affect critical data paths or transactions? Operational Risk Does this impact auth, billing, messaging, or infra? Testability Can this be reliably unit + integration tested? Score Formula Range: -10 → +10 Interpretation BFRI Meaning Action -------- --------- ---------------------- 6–10 Safe Proceed 3–5 Moderate Add tests + monitoring 0–2 Risky Refactor or isolate < 0 Dangerous Redesign before coding --- When to Use Automatically applies when working on: Routes, controllers, services, repositories Express middleware Prisma database access Zod validation Sentry error tracking Configuration management Backend refactors or migrations --- 2. Core Architecture Doctrine (Non-Negotiable) 1. Layered Architecture Is Mandatory No layer skipping No cross-layer leakage Each layer has one responsibility --- 2. Routes Only Route Routes must contain zero business logic. --- 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/backend-dev-guidelines--143c08