Agent skill · software engineering · jeremylongshore
salesforce-architecture-variants
Analyze Salesforce direct API, middleware, event-driven, replicated-data, and hybrid integration architectures against explicit constraints. Use when making architecture decisions. Trigger with "compare Salesforce architectures".
Why this skill is useful
Provides specific architectural patterns and code examples for Salesforce integrations that the AI wouldn't reliably generate on its own.
What it needs
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
Salesforce Integration Architecture Variants Overview Produce a falsifiable architecture decision that explains why one interaction pattern fits each use case and which tradeoffs remain. Prerequisites Use cases, business invariants, sources of truth, consumers, latency, volume, ordering, consistency, and recovery needs Org products, APIs, events, limits, identities, data classes, residency, retention, support, and existing platforms Security, operability, cost, skills, vendor, migration, lock-in, disaster recovery, and change-control constraints 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 documents remote process, batch, data synchronization, and event integration patterns. Direct REST, composite, bulk, Pub/Sub or CDC, middleware, event relay, and replicated read models differ in coupling, consistency, capacity, and recovery. Authentication Model client apps, OAuth flows, principals, scopes, CRUD and field access, sharing, secret custody, rotation, revocation, and break-glass separately for every variant. Instructions 1. Write decision drivers and non-negotiable invariants before naming a preferred technology. 2. Model direct synchronous API, managed or customer middleware, Salesforce events, scheduled bulk, replicated data, and hybrid variants. 3. For each, trace authority, data and event flow, transactions, ordering, idempotency, limits, failure isolation, reconciliation, and recovery. 4. Evaluate security, privacy, residency, audit, operability, latency, throughput, cost, skills, vendor support, and lock-in with evidence. 5. Run threat, failure, capacity, data-correctness, and migration exercises against the leading variants. 6. Prototype the riskiest assumption with synthetic data in the lowest-risk authorized environment. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-architecture-variants