Provider Setup
Configure existing support first. Add adapter code only when support is really missing.
VibeKit separates provider setup from provider implementation.
Use the focused provider skills for supported authentication, email, payment, storage, AI and analytics providers. The agent checks existing support, required credentials, selection precedence and the real workflow that must be verified.
Use add-provider for a missing non payment adapter. Use add-a-payment-provider for a new payment processor.
A complete new adapter belongs in the package that owns the service. It needs configuration guidance, runtime selection, failure handling and focused tests.
Saved credentials or a green connection check do not prove the user workflow. Before launch, test the selected provider on the final domain.