What problem does it solve? Choosing and implementing the right Salesforce integration pattern is error-prone: callouts fail after DML, secrets leak into code, retries loop forever, and inbound APIs get picked by familiarity instead of fit. This Skill provides pattern selection guidance, production-grade Apex implementations, and verification commands for both inbound and outbound integrations. ## Core Features & Use Cases - Pattern Selection: Decision tables map latency, volume, and transactionality requirements to the six official Salesforce integration patterns (Request-Reply, Fire and Forget, Batch Sync, Remote Call-In, UI Update, Data Virtualisation). - Outbound Integration: Named Credential and External Credential setup, Queueable callouts with Finalizer-based retry, exponential backoff, dead-letter queues, and idempotency keys. - Inbound APIs: REST, Composite, Composite Graph, sObject Collections, Bulk API 2.0, Apex REST, GraphQL, and Pub/Sub API with limits and curl/sf CLI examples. - Testing & Verification: HttpCalloutMock router mocks, platform event tests, and post-deploy smoke probes against real orgs. - Use Case: A story requires syncing orders to an external billing system. The Skill guides you to a fire-and-forget platform event pattern, provides the publisher Apex, a retryable subscriber with dead-lettering, and the sf CLI commands to verify the integration in a sandbox. ## Quick Start Ask the assistant to design an integration that calls an external billing API from Salesforce using a named credential with retry and dead-letter handling.