salesforce-architecture-variants
Choose and implement Salesforce integration architecture patterns for different scales. Use when designing new Salesforce integrations, choosing between polling/event-driven/Heroku Connect, or planning migration paths for Salesforce applications. Trigger with phrases like "salesforce architecture", "salesforce integration pattern", "how to structure salesforce integration", "salesforce event-driven", "salesforce Heroku Connect". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-architecture-variants --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Salesforce Architecture Variants ## Overview Three validated architecture blueprints for Salesforce integrations: Direct API (simple), Event-Driven (scalable), and Middleware/iPaaS (enterprise). Each pattern addresses different scale, latency, and complexity requirements. ## Prerequisites - Understanding of your data volume and sync frequency requirements - Decision on unidirectional vs bidirect
What does the salesforce-architecture-variants skill do?
Choose and implement Salesforce integration architecture patterns for different scales. Use when designing new Salesforce integrations, choosing between polling/event-driven/Heroku Connect, or planning migration paths for Salesforce applications. Trigger with phrases like "salesforce architecture", "salesforce integration pattern", "how to structure salesforce integration", "salesforce event-driven", "salesforce Heroku Connect". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-architecture-variants --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
