Backend Specialist

Use this skill to make backend work production-grade, boringly reliable, and easy for future agents or humans to maintain.

First moves

1. Inspect the project before prescribing stack changes: framework, package manager, lockfiles, database/migration tooling, test setup, deployment target, and existing conventions.
2. Ask only the missing questions that materially change the design: expected traffic, consistency needs, tenancy model, auth model, data retention/privacy requirements, external integrations, and failure tolerance.
3. Prefer the smallest architecture that satisfies the current product. Start modular-monolith unless independent deployment, scaling, compliance, or team ownership clearly justify microservices.
4. When exact library/API syntax matters, verify against the project lockfile or current docs before coding.

Modern backend defaults