Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/salesforce-development
Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP).
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
and 2 more in the full report
5 fixed17 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are ready to deploy metadata from our source directory force-app to our Salesforce production environment target-org 'my-prod'. We want to run local Apex tests first during validation, and then execute a quick deployment to save time. What exact Salesforce CLI commands should we execute?
| Checked | Without skill | With skill |
|---|---|---|
| The first command uses sf project deploy validate with --test-level RunLocalTests. | Missed | Passed |
| The second command uses sf project deploy quick with --job-id. | Passed | Passed |
The instructions your model reads when the skill loads.
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).
For current Apex development, make the intended data-access mode explicit.
WITH USER_MODE for SOQL/SOSL that should enforce the running user's object permissions, FLS, sharing, and other supported security controls.Database methods when the operation should enforce user permissions.WITH SECURITY_ENFORCED is legacy guidance and should not be used for new API 67.0+ code.Choose an integration pattern based on latency, volume, ownership, and reliability requirements:
| Requirement | Preferred pattern |
|---|---|
| Synchronous request/response | REST or Composite API |
| Large asynchronous data movement | Bulk API 2.0 |
| Publish business events | Platform Events |
| Detect Salesforce record changes | Change Data Capture |
| High-scale event consumption | Pub/Sub API |
| Salesforce outbound authentication | Named Credentials / External Credential |
| New OAuth client configuration | External Client App |
Do not select an API only because a record-count threshold is crossed. Evaluate data volume, latency, transaction boundaries, retry behavior, error handling, and monitoring.
Prefer events over continuous polling when the platform and integration support it.
Bulk API 2.0 supports event-driven job status and result notifications through Pub/Sub API, including partial query results. Use polling only when event-driven processing is unavailable or unnecessary.
For asynchronous external calls, design for idempotency. A timeout does not prove that the remote operation failed; retrying a non-idempotent request can create duplicates.
test cases passed, vs 17 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.