A Claude Code plugin providing best-practice guidance for Salesforce developers, admins, and architects/consultants, plus a digest of the last 10 platform releases (Summer '23 → Summer '26).
| Skill | Use it for |
|---|---|
sfdc-developer-best-practices |
Apex, LWC/Aura, SOQL, async patterns, integrations, DevOps/CI-CD |
sfdc-admin-best-practices |
Flow/automation, data model, sharing & security, declarative-first design, release management |
sfdc-architect-solutioning |
Well-Architected Framework, integration/data architecture, proposing solutions to business stakeholders |
sfdc-release-notes-digest |
"What's new," deprecations, and migration impact across the last 10 releases (per-release detail in references/) |
Install like any local plugin: point Claude Code at this directory (or publish it to a marketplace) and the skills activate automatically when their description trigger matches the task at hand.
Content was researched live (July 2026) against official Salesforce sources (developer.salesforce.com, trailhead.salesforce.com, architect.salesforce.com, help.salesforce.com, admin.salesforce.com) via a multi-agent research workflow, then synthesized into skill form. Two access realities discovered during research, worth knowing when judging trust:
help.salesforce.comis a JS single-page app — direct automated fetches often only receive a "Loading" placeholder rather than real content. Where that happened, research fell back to search snippets of the same official pages, or to reputable secondary sources (Salesforce Ben, Salesforce Admins blog "Release in a Box," SFXD wiki, Automation Champion) to corroborate.- Official release-note PDFs return HTTP 403 to automated fetches (bot protection), and
resources.docs.salesforce.comwas unreachable from this environment (TLS errors) — so release content was gathered via search + corroboration rather than raw PDF parsing.
Every domain skill's ## Sources section and every release file's ## Sources section lists exactly what was consulted and how (direct-fetch / search-snippet / secondary-corroboration), so you can judge confidence per claim.
Release notes sourcing summary — 7 of 10 releases had an official primary source directly confirmed; Summer '23, Summer '24, and Summer '26 relied on secondary corroboration only (see each file's primarySourceFound note):
| Release | Primary source confirmed? |
|---|---|
| Summer '23 | No — secondary corroboration only |
| Winter '24 | Yes |
| Spring '24 | Yes |
| Summer '24 | No — secondary corroboration only |
| Winter '25 | Yes |
| Spring '25 | Yes |
| Summer '25 | Yes |
| Winter '26 | Yes |
| Spring '26 | Yes |
| Summer '26 | No — secondary corroboration only |
Caveat: this reflects one research pass, not exhaustive scraping of "everything" on Salesforce's sites. Treat it as a strong starting point — spot-check anything business-critical against the live official docs before relying on it, and re-run the research periodically as Salesforce ships new releases.