backend-dev-kit

Implement JWT authentication with jose and argon2 — register, login token, refresh rotation, GET /me, requireAuth and requireRole middleware. Use when adding login, access/refresh tokens, or route guards, not for generic CRUD resources.

Builds one Express API resource increment from a spec-dev-kit spec (and optional html-generator-kit prototype) — scoped UPSTREAM_SPEC import of entities and api-surface, hub-and-spoke (scaffold-service if needed, Zod, Drizzle, repository, service, router, OpenAPI, Vitest), quality gates, and a mandatory human review. Writes kit-result.json. Never opens a PR. Use when implementing a backend resource from an approved spec, not for a greenfield tree alone (that is scaffold-service) and not for adding a resource without a spec (that is express-feature).

Drizzle ORM patterns for common data access — keyset pagination, filtering, bulk operations, upsert, soft delete, and optimistic locking with a version column.

Implement structured error handling in Express — AppError hierarchy, Zod 422 mapping, RFC 7807-shaped JSON, pino, and request-id middleware.

Scaffold and implement a complete Express feature slice — Zod schemas, Drizzle table, repository, service, router, and tests — following the three-layer architecture.

Write Vitest HTTP integration tests for an Express router or service using supertest against createApp(), Testcontainers PostgreSQL, and Drizzle test factories.

Generate OpenAPI from Zod schemas with @asteasolutions/zod-to-openapi and serve Swagger UI at /docs and /openapi.json. Use when adding API docs, operationId, or OpenAPIRegistry wiring, not when scaffolding a CRUD resource.

Wire Redis for cache-aside, BullMQ background jobs, and express-rate-limit store — official redis client, PING on /readyz, serializable job IDs. Use when adding caching, durable queues, or clustered rate limits, not for Drizzle queries.

Scaffold a Node.js TypeScript Express service — package.json, createApp factory, compose.ts, Drizzle client, Zod env, middleware, drizzle-kit, and .env.example. Use when creating the initial directory structure for a new backend API, not when adding a resource to an existing tree.