Agent skill · product strategy · jeremylongshore
salesforce-reference-architecture
Design a governed Salesforce integration architecture with explicit authority, identity, API, event, data, evidence, limit, and recovery boundaries. Use when conducting architecture reviews. Trigger with "design Salesforce architecture".
Why this skill is useful
Provides specific architectural patterns and project structures for Salesforce integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires jsforce, sfdx-cli installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Governed Salesforce Integration Reference Architecture Overview Create an evidence-backed target architecture that names every source of truth, mutation path, principal, data class, failure boundary, and recovery mechanism. Prerequisites Business capabilities, system context, sources of truth, data owners, consumers, service objectives, and constraints Org topology, Salesforce products, External Client Apps or existing Connected Apps, APIs, events, limits, and entitlements Security, privacy, residency, retention, reconciliation, disaster recovery, support, and change-control requirements 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 provides multiple synchronous, asynchronous, bulk, composite, and event integration surfaces with org-specific availability and limits. No single direct API, middleware, replicated database, or event pattern is correct for every domain. Authentication Model human, integration, deployment, diagnostic, and break-glass principals separately. Bind each to an approved app, OAuth flow, minimum permissions, secret custody, rotation, revocation, and audit path. Instructions 1. Map systems, trust zones, sources of truth, record and event ownership, consumers, data classes, and business invariants. 2. Inventory orgs, products, editions, packages, schemas, API versions, events, limits, identities, and operational dependencies. 3. Select interaction patterns per use case: synchronous request, asynchronous bulk, composite, event, scheduled reconciliation, or replicated read model. 4. Define contracts for schema, versioning, idempotency, ordering, pagination, checkpoints, retries, dead letters, and backfills. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-reference-architecture