Adapter reference
Find the native integration for each capability without introducing a universal adapter layer.
Choose adapters by capability
- Services, Database, Authentication, Storage and SMTP own application setup.
- Models, MCP Tools and Redis Workers own execution integration.
Extend the seam you actually need
Implement the owning capability's adapter contract rather than a universal adapter interface. Preserve lifecycle, cancellation, JSON validation and uncertain-outcome semantics. Native libraries remain explicit dependencies.
Passing local contract tests does not qualify every remote deployment or upstream API. Native page routing remains external; router-tanstack is not part of this selection. Cloud services and Payments are outside this candidate scope.
For renderer integration and styling, use Whisk documentation without duplicating it here.