saas-dev:backend-wirer

To generate Express routes and Drizzle schemas from a backend spec, the skill translates BackendSpec definitions into code while using brownfield-aware collision detection to safely avoid overwriting existing endpoints and tables in your SaaS project.

Running idempotent Postgres migrations against Neon PostgreSQL involves generating Drizzle table and Zod schema code, then producing and executing DDL migrations designed to safely apply schema changes without breaking existing brownfield database tables.

Yes, backend wiring supports integration testing by generating endpoint tests using supertest and executing a three-cycle test-fix-rerun loop with AI-assisted repair to validate and automatically recover from issues in the generated code.

Yes, you can inject TanStack Query hooks automatically when adding new backend endpoints, as the backend wiring process translates BackendSpec definitions into hook injections alongside Express routes and Drizzle storage functions.

The best way to refactor brownfield backend code without causing collisions is using a backend wiring process that scans existing routes, schemas, and storage functions to detect conflicts before safely generating new API implementations.

Automated Postgres migrations may fail if DDL is not idempotent or if collision detection is missing, which is why this backend wiring generates idempotent migration SQL and scans existing schemas before applying changes to a brownfield database.