Backend Dev Guidelines

This is a backend architecture rulebook disguised as a Claude skill. It enforces layered architecture (routes, controllers, services, repositories), mandatory Zod validation on all inputs, Sentry for every error, and a centralized config system instead of raw process.env calls. Before you write code, you calculate a Backend Feasibility & Risk Index across five dimensions to decide if you should proceed, refactor, or redesign. It's opinionated in the best way: no business logic in routes, no skipping layers, no untested services. If you're tired of Express codebases turning into spaghetti after six months, this gives you guard rails that actually prevent the common mistakes. Works best when you're building or maintaining Node.js microservices where consistency and observability matter more than moving fast and breaking things.

skills.sh installs: 1.5K
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill backend-dev-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Files

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

Use these patterns when they fit the target repository; its architecture, authorization model and dependency versions take precedence. This documentation does not ship a runnable service.