salesforce-development

Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, External Client Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP).

By sickn33 · 598 installs

npx skills add sickn33/agentic-awesome-skills --skill salesforce-development

Source repository · Upstream listing

Salesforce Development Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, External Client Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP). Detailed Guide Read [the detailed guide](references/detailed guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end to end work, read the guide completely. When to Use User mentions or implies: salesforce User mentions or implies: sfdc User mentions or implies: apex User mentions or implies: lwc User mentions or implies: lightning web components User mentions or implies: sfdx User mentions or implies: scratch org User mentions or implies: visualforce User mentions or implies: soql User mentions or implies: governor limits User mentions or implies: connected app Limitations Examples are incomplete fragments, not deployment ready packages: custom fields/classes, CSV parsing, abort handling, imports, result typing and security tests are omitted. Confirm org/API version, CRUD/FLS/sharing, callout/job limits and user/system mode explicitly. Use test orgs and synthetic data; production deployment and package promotion require the approved target/change process. Do not send outbound Slack/CRM data merely because a trigger example includes it. Salesforce platform behavior and API versions change frequently; verify current official documentation before implementing version sensitive features. Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.