Agent skill · Databases

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.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill backend-dev-guidelines --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 12
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/backend-dev-guidelines/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 Form

What's inside
Steps it walks through
  1. 1. Backend Feasibility & Risk Index (BFRI)
  2. BFRI Dimensions (1–5)
  3. Score Formula
  4. Interpretation
  5. When to Use
  6. 2. Core Architecture Doctrine (Non-Negotiable)
  7. 1. Layered Architecture Is Mandatory
  8. 2. Routes Only Route
  9. 3. Controllers Coordinate, Services Decide
  10. 4. All Controllers Extend BaseController
  11. 5. All Errors Go to Sentry
  12. 6. unifiedConfig Is the Only Config Source
  13. 7. Validate All External Input with Zod
  14. 3. Directory Structure (Canonical)
Ships with 11 files
  • resources/architecture-overview.md
  • resources/async-and-errors.md
  • resources/complete-examples.md
  • resources/configuration.md
  • resources/database-patterns.md
  • resources/middleware-guide.md
  • resources/routing-and-controllers.md
  • resources/sentry-and-monitoring.md
  • resources/services-and-repositories.md
  • resources/testing-guide.md
  • resources/validation-patterns.md
More from agentic-awesome-skills
All skills →
About this skill
What does the backend-dev-guidelines skill do?

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.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill backend-dev-guidelines --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going