Skip to content

Backend Dev Guidelines

Teaches the agent Node.js/Express/TypeScript backend conventions: layered routes, controllers, services, Prisma, Sentry, Zod.

Stars
10,043
Licence
MIT
Files
12 files

What it does

When you ask an AI agent to build or change a Node.js/Express/TypeScript backend, this skill gives it a set of house rules to follow. The agent will put route definitions in thin route files, move logic into controllers, services and repositories, validate input with Zod, read settings from a unifiedConfig module instead of process.env, and report errors to Sentry. The skill is only reference material (markdown guides and code examples); it does not run anything itself.

Great for

  • Backend developers on Node.js/Express/TypeScript teams who want consistent code structure
  • Teams using Prisma, Sentry and Zod who want an agent to follow their conventions
  • Developers migrating older Express code toward a layered architecture

Skip it if

  • Projects on a different stack (Python, Go, Django); the guide says to adapt the principles yourself, and the examples will not match
  • Teams whose conventions differ from these patterns (for example, not using unifiedConfig or BaseController), since the agent may impose code that does not fit their codebase

Try asking

  • “Add a new REST endpoint for managing user subscriptions, following our controller and service layers”
  • “Refactor this Express route file so business logic moves into a service with dependency injection”
  • “Set up a new microservice skeleton with instrument.ts, unifiedConfig and Sentry error handling”
  • “Write Jest unit and integration tests for this repository class”
Step-by-step guide: how to use Backend Dev GuidelinesInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 12 original files, the MIT licence and an attribution note.

    backend-dev-guidelines.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip backend-dev-guidelines.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip backend-dev-guidelines.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Point the agent at your own project's conventions too; the guide is written for one example microservice layout and may conflict with your existing structure.
  • Check generated code against the referenced files, since examples such as BaseController and unifiedConfig must exist in your project to compile.
  • Review any Sentry and config changes, because the examples show patterns that send error data to a third-party service and rely on environment-specific settings.

What's inside

  • 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
  • SKILL.md

Redistributed unmodified from diet103/claude-code-infrastructure-showcase under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.