What problem does it solve?
Scala tasks frequently stall due to choosing the right effect system, HTTP framework, and safety patterns, leading to inconsistent architecture, brittle error handling, and harder-than-necessary testing.
Core Features & Use Cases
- Effect-System Guidance (ZIO / Cats Effect / Akka / Direct Style): Choose an approach that matches your concurrency, dependency-injection, error modeling, and team conventions.
- HTTP Framework Selection (Tapir / http4s / Play / zio-http / Vert.x): Build routes and endpoints that fit your streaming, type-safety, and full-stack needs.
- Implementation & Review Verification Checklist: Validate compilation/tests, enforce type safety, manage resources, and confirm OpenAPI generation for Tapir workflows.
- Use Case: You’re implementing a Scala 3 backend with typed errors, resource-safe DB access, and HTTP endpoints that should generate OpenAPI docs, while keeping concurrency behavior and testing strategy correct.
Quick Start
Use the scala skill to design a ZIO 2 + Tapir service in Scala 3.5 with typed errors, resource-safe DB access, and a verification plan that includes compile and test gates.