backend-service-scaffolding

Scaffolding a backend service with tenant isolation and Zod validation generates service files under packages/backend/src/services, wires exports, and enforces tenant-aware queries to ensure a consistent project structure.

Generating unit tests for CRUD operations in a backend monorepo uses automated templates that mock the Supabase client and validate tenant-context aware queries, ensuring robust and isolated test coverage for new domain services.

The backend service scaffolding workflow requires a centralized logger to enforce audit logging for CRUD operations, ensuring all tenant-context aware queries and data modifications are properly tracked.

This scaffolding workflow adds audit logging to CRUD operations by generating new service files with built-in audit logging capabilities, ensuring consistent project structure from the start rather than retrofitting existing services.

Enforcing runtime validation with Zod when creating new domain services is automated by the scaffolding workflow, which injects Zod validation directly into the generated service files for all input handling and CRUD operations.

Scaffolded backend service tests need to mock the Supabase client to validate tenant-context aware queries in isolation, preventing live database calls and maintaining consistent unit test behavior across entities.