effect

Model expected failures as typed errors rather than unchecked exceptions so callers can handle them exhaustively. This makes failure cases part of the function signature and keeps error paths explicit across the service.

Build dependencies as explicit layers and provide them at the application boundary. This keeps service composition declarative and lets the runtime wire database, configuration, and external clients without hidden globals.

Yes, but keep promise, callback, and request-framework interop at narrow adapter boundaries. Isolate the conversion code so the core application logic stays purely within Effect's model.

Use scoped resources for connections, handles, and subscriptions that require cleanup. Effect guarantees finalizers run when the scope closes, preventing leaked resources even on failure paths.

Run the repository's formatter and linter first, then bun typecheck and the focused tests. This ordering catches style issues before type errors and confirms the service compiles under Bun's toolchain.