backend-dev-guidelines

name	backend-dev-guidelines
description	ALWAYS use this when implementing or reviewing backend routes, controllers, services, repositories, middleware, validation, or data-access layers in a production-style Node.js/TypeScript service.

Backend Development Guidelines

Selective Reading Rule

Start with:

• references/usage-routing.md
• references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

Selective Reading Rule

Start with:

• references/senior-master-standard.md
• references/layering-and-boundaries.md
• references/reliability-checklist.md

Then follow the rest of the skill only for the architectural slice that matches the task.

(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