Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows backend-dev-guidelines

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.

1783 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

You are a senior backend engineer operating production-grade services under strict architectural and reliability constraints

When to use it

Automatically applies when working on:

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Backend Development Guidelines; 1. Backend Feasibility & Risk Index (BFRI); BFRI Dimensions (1–5); Score Formula; Interpretation; When to Use.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

Backend Development Guidelines1. Backend Feasibility & Risk Index (BFRI)BFRI Dimensions (1–5)Score FormulaInterpretationWhen to Use2. Core Architecture Doctrine (Non-Negotiable)1. Layered Architecture Is Mandatory2. Routes Only Route3. Controllers Coordinate, Services Decide4. All Controllers Extend `BaseController`5. All Errors Go to Sentry

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
backend-dev-guidelines
description
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "backend-dev-guidelines" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-e3f5639acf2390d0-Backend-Dev-Guidelines.html
Save it as .cursor/skills/backend-dev-guidelines/SKILL.md or .claude/skills/backend-dev-guidelines/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/sickn33/agentic-awesome-skills' --list

npx skills add 'https://github.com/sickn33/agentic-awesome-skills' --skill 'backend-dev-guidelines'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: backend-dev-guidelines description: "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." risk: critical source: community date_added: "2026-02-27" --- # 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 ``` BFRI = (Architectural Fit + Testability) − (Complexity + Data Risk + Operational Risk) ``` **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 ``` Routes → Controllers → Services → Repositories → Database ``` * No layer skipping * No cross-layer leakage * Each layer has **one responsibility** --- ### 2. Routes Only Route ```ts // ❌ NEVER router.post('/create', async (req, res) => { await prisma.user.create(...); }); // ✅ ALWAYS router.post('/create', (req, res) => userController.create(req, res) ); ``` Routes must contain **zero business logic**. --- ### 3. Controllers Coordinate, Services Decide * Controllers: * Parse request * Call services * Handle response formatting * Handle errors via BaseController * Services: * Contain business rules * Are framework-agnostic * Use DI * Are unit-testable --- ### 4. All Controllers Extend `BaseController` ```ts export class UserController extends BaseController { async getUser(req: Request, res: Response): Promise { try { const user = await this.userService.getById(req.params.id); this.handleSuccess(res, user); } catch (error) { this.handleError(error, res, 'getUser'); } } } ``` No raw `res.json` calls outside BaseController helpers. --- ### 5. All Errors Go to Sentry ```ts catch (error) { Sentry.captureException(error); throw error; } ``` ❌ `console.log` ❌ silent failures ❌ swallowed errors --- ### 6. unifiedConfig Is the Only Config Source ```ts // ❌ NEVER process.env.JWT_SECRET; // ✅ ALWAYS import { config } from '@/config/unifiedConfig'; config.auth.jwtSecret; ``` --- ### 7. Validate All External Input with Zod * Request bodies * Query params * Route params * Webhook payloads ```ts const schema = z.object({ email: z.string().email(), }); const input = schema.parse(req.body); ``` No validation = bug. --- ## 3. Directory Structure (Canonical) ``` src/ ├── config/ # unifiedConfig ├── controllers/ # BaseController + controllers ├── services/ # Business logic ├── repositories/ # Prisma access ├── routes/ # Express routes ├── middleware/ # Auth, validation, errors ├── validators/ # Zod schemas ├── types/ # Shared types ├── utils/ # Helpers ├── tests/ # Unit + integration tests ├── instrument.ts # Sentry (FIRST IMPORT) ├── app.ts # Express app └── server.ts # HTTP server ``` --- ## 4. Naming Conventions (Strict) | Layer | Convention | | ---------- | ------------------------- | | Controller | `PascalCaseController.ts` | | Service | `camelCaseService.ts` | | Repository | `PascalCaseRepository.ts` | | Routes | `camelCaseRoutes.ts` | | Validators | `camelCase.schema.ts` | --- ## 5. Dependency Injection Rules * Services receive dependencies via constructor * No importing repositories directly inside controllers * Enables mocking and testing ```ts export class UserService { constructor( private readonly userRepository: UserRepository ) {} } ``` --- ## 6. Prisma & Repository Rules * Prisma client **never used directly in controllers** * Repositories: * Encapsulate queries * Handle transactions * Expose intent-based methods ```ts await userRepository.findActiveUsers(); ``` --- ## 7. Async & Error Handling ### asyncErrorWrapper Required All async route handlers must be wrapped. ```ts router.get( '/users', asyncErrorWrapper((req, res) => controller.list(req, res) ) ); ``` No unhandled promise rejections. --- ## 8. Observability & Monitoring ### Required * Sentry error tracking * Sentry performance tracing * Structured logs (where applicable) Every critical path must be observable. --- ## 9. Testing Discipline ### Required Tests * **Unit tests** for services * **Integration tests** for routes * **Repository tests** for complex queries ```ts describe('UserService', () => { it('creates a user', async () => { expect(user).toBeDefined(); }); }); ``` No tests → no merge. --- ## 10. Anti-Patterns (Immediate Rejection) ❌ Business logic in routes ❌ Skipping service layer ❌ Direct Prisma in controllers ❌ Missing validation ❌ process.env usage ❌ console.log instead of Sentry ❌ Untested business logic --- ## 11. Integration With Other Skills * **frontend-dev-guidelines** → API contract alignment * **error-tracking** → Sentry standards * **database-verification** → Schema correctness * **analytics-tracking** → Event pipelines * **skill-developer** → Skill governance --- ## 12. Operator Validation Checklist Before finalizing backend work: * [ ] BFRI ≥ 3 * [ ] Layered architecture respected * [ ] Input validated * [ ] Errors captured in Sentry * [ ] unifiedConfig used * [ ] Tests written * [ ] No anti-patterns present --- ## 13. Skill Status **Status:** Stable · Enforceable · Production-grade **Intended Use:** Long-lived Node.js microservices with real traffic and real risk --- ### When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…