Skip to content
Skills Library
Programming · Building & coding

salesforce-sdk-patterns

/salesforce-sdk-patterns

Build a version-negotiated Salesforce adapter around the customer-selected CLI or client library with typed boundaries and contract tests. Use when standardizing application access. Trigger with "design a Salesforce adapter".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a version-negotiated Salesforce adapter around the customer-selected CLI or client library with typed boundaries and contract tests. Use when standardizing application access. Trigger with "design a Salesforce adapter".

Triggers from the description

design a Salesforce adapter

Arguments

/salesforce-sdk-patterns [repository] [adapter-path]
Original author description

Build a version-negotiated Salesforce adapter around the customer-selected CLI or client library with typed boundaries and contract tests. Use when standardizing application access. Trigger with "design a Salesforce adapter".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Example
Original SKILL.md headings · 67 lines, 460 words
SKILL.md preview
---
name: salesforce-sdk-patterns
description: 'Build a version-negotiated Salesforce adapter around the customer-selected CLI or client library with typed boundaries and contract tests. Use when standardizing application access. Trigger with "design a Salesforce adapter".'
argument-hint: "[repository] [adapter-path]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [saas, salesforce, adapter, sdk, typescript]
model: inherit
effort: high
compatibility: Designed for Claude Code; dependency changes and live API probes require application owner and Salesforce admin approval
---
# Salesforce Typed Adapter and Client-Library Boundary

## Overview

Contain library churn and org-specific schema behind a small adapter whose types, API version, permissions, retries, and evidence are explicit.

## Prerequisites

- Repository, runtime, supported environments, and selected Salesforce library or CLI
- Current dependency lock, org schema evidence, API support policy, and error samples
- Application, Salesforce platform, security, and data owners

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect approved repository and evidence files, `WebFetch` to re-check current first-party Salesforce documentation, and `Write` or `Edit` only for secretless plans, fixtures, configuration, and redacted receipts.

## Current Contract

Salesforce publishes versioned API contracts, while third-party client libraries have independent release and support policies. Object and field shapes remain customer-specific, so generated or handwritten types must be tied to dated metadata evidence.

## Authentication

Accept an authenticated client or secret reference from the approved authorization layer. The adapter must not invent a password fallback, persist tokens, broaden scopes, or choose a production org implicitly.

## Instructions

1. Inventory direct Salesforce calls, library versions, API versions, objects, fields, mutations, retries, and error handling.
2. Define a narrow adapter interface for identity, metadata discovery, reads, bounded writes, async jobs, and limits.
3. Bind types to dated object metadata or a governed schema snapshot and label nullable, encrypted, formula, and inaccessible fields.
4. Centralize pagination, request IDs, timeouts, idempotency keys or external IDs, error normalization, and redaction.
5. Add contract fixtures for success, partial failure, token expiry, permission denial, schema drift, limits, and timeouts.
6. Test the adapter without a live org, then run approved read-only and sandbox mutation probes.
7. Migrate callers incrementally and retain a reversible compatibility boundary until evidence is complete.

## Approval Boundaries

Do not upgrade dependencies, change API versions, regenerate broad schemas, or perform live writes without code owner, platform owner, and data owner approval.

## Output

Return the adapter contract, dependency and API matrix, schema provenance, fixture coverage, migration plan, live probe receipt, and rollback boundary.

## Error Handling

| Condition | Response |
|---|---|
| Library behavior differs from Salesforce documentation | Pin the discrepancy, reproduce at the raw API boundary, and escalate upstream before broad rollout. |
| Schema snapshot is stale | Block generated-type use until metadata is refreshed and reviewed. |
| Caller bypasses the adapter | Fail the policy check or document a time-bounded exception with an owner. |

## Example

A redacted completion receipt might look like this:

```text
adapter=SalesforceGateway; api=discovered-supported; schema=dated; fixtures=8; sandbox-write=approved-pass; bypasses=0
```

## Resources

- [Salesforce REST API EOL policy](https://developer.salesforce.com/docs/platform/api-rest/guide/api-rest-eol.html)
- [REST API resources](https://developer.salesforce.com/docs/platform/api-rest/guide/resources-list.html)

## Next Steps

Run the workflow first in the lowest-risk authorized org and preserve its redacted receipt. Schedule a review against the next Salesforce seasonal release and the customer change calendar.

Versions

The database has no other skills named salesforce-sdk-patterns.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 7c00bfe60165 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100miro-sdk-patterns
    Choose and implement Miro Node client or raw REST adapter patterns with typed boundaries, pagination, tenant isolation, and explicit operator commands. Use when designing a Miro API adapter. Trigger with \"review Miro SDK pattern\".
  • 100workhuman-sdk-patterns
    Design a typed Workhuman integration adapter from customer-authorized API or connector contracts without assuming a public SDK. Use when creating reusable client boundaries. Trigger with "design a Workhuman adapter".
  • 100platform-salesforce-connect-adapter-generate
    Custom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or copying. TRIGGER when: connecting a non-standard external API, writing a DataSource.Provider/Connection or a…
  • 90salesforce-architecture
    Use for org-level Salesforce architecture work — capacity planning, security/sharing review, integration patterns, multi-org strategy, tech-debt assessment.
  • 100specialized-salesforce-architect
    Use when Codex should act as the Salesforce Architect specialist from Agency Agents. Solution architecture for Salesforce platform — multi-cloud design, integration patterns, governor limits, deployment strategy, and data model governance for enterprise-scale orgs
  • 100ship-adapter
    Port schemas, interfaces, and API contracts into adapters. Use when writing a DB adapter, API client wrapper, interface adapter, or data transformer.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.