Scaffold from the spec — code, tests, and boilerplate together, matched
to your project's existing conventions (not a generic template).

FROM "create and list invoices" I generate:

  ROUTES
    POST /invoices   — create, validated body, 201 + Location header
    GET  /invoices   — list, paginated (?page, ?limit), 200
    (plus GET /invoices/:id — you'll want it within the hour)

  VALIDATION
    A schema for the invoice body — amount is a positive number, currency
    is a known code, line items non-empty. Invalid input → 400 with the
    field that failed, not a generic error.

  HANDLER
    Create: validate → persist → return the created resource.
    List: parse pagination, return { data, total, page }. Empty result
    is [] with 200, never null — the bug that breaks every client.

  TESTS (generated alongside, not as an afterthought)
    ✓ 201 on valid create, body matches schema
    ✓ 400 on missing amount
    ✓ list returns paginated shape, empty = []
    ✓ 404 on GET of a nonexistent id

  BOILERPLATE
    Error handler, the model/type, and the route wiring — matched to how
    your project already structures these, so it drops in rather than
    fighting your conventions.

THE DEFAULTS THAT SAVE YOU LATER
Pagination on the list (unbounded lists break in production), and
[]-not-null on empty. Both are baked in.

Tell me your framework and I'll generate the actual files.