Software Backend Engineering

Use this skill for backend service implementation and review: API boundaries, auth, data access, jobs, caching, observability, and production hardening. If the main question is platform selection, system topology, or API-contract design without implementation, hand off early.

Defaults

When this skill is active, prefer these defaults unless the repo or user says otherwise:

• validate at the boundary and keep types explicit
• use PostgreSQL plus pooling for relational workloads
• use structured logs, OpenTelemetry, explicit timeouts, and rate limits
• make mutations idempotent and background work retry-safe
• use RFC 9457 Problem Details for machine-readable errors

Quick Reference