Skip to content
Skills Library
Programming · Automation

salesforce-local-dev-loop

/salesforce-local-dev-loop

Build a repeatable Salesforce DX development loop using source format, synthetic tests, and an authorized scratch org or sandbox. Use when changing metadata or integration code. Trigger with "build a Salesforce dev loop".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a repeatable Salesforce DX development loop using source format, synthetic tests, and an authorized scratch org or sandbox. Use when changing metadata or integration code. Trigger with "build a Salesforce dev loop".

Triggers from the description

build a Salesforce dev loop

Arguments

/salesforce-local-dev-loop [project-path] [org-alias]
Original author description

Build a repeatable Salesforce DX development loop using source format, synthetic tests, and an authorized scratch org or sandbox. Use when changing metadata or integration code. Trigger with "build a Salesforce dev loop".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Example
Original SKILL.md headings · 67 lines, 452 words
SKILL.md preview
---
name: salesforce-local-dev-loop
description: 'Build a repeatable Salesforce DX development loop using source format, synthetic tests, and an authorized scratch org or sandbox. Use when changing metadata or integration code. Trigger with "build a Salesforce dev loop".'
argument-hint: "[project-path] [org-alias]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [saas, salesforce, salesforce-dx, scratch-org, testing]
model: inherit
effort: high
compatibility: Designed for Claude Code; org creation, metadata deployment, and test-data loading require Dev Hub and administrator authorization
---
# Salesforce DX Local Development Loop

## Overview

Create a source-driven loop that separates static and synthetic checks from explicitly authorized org validation and leaves no unmanaged test data.

## Prerequisites

- A Salesforce DX project or an approved migration plan to source format
- An authorized Dev Hub and scratch-org definition, or a dedicated development sandbox
- Synthetic fixtures, test owner, cleanup policy, and current Salesforce CLI contract

## 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 DX supports source-driven development and scratch orgs configured through project definitions; org availability, features, limits, duration, namespaces, and sandbox alternatives depend on the customer environment.

## Authentication

Use a named CLI alias backed by the approved OAuth path. Never commit authorization files, access tokens, private keys, usernames, org IDs, or generated user passwords.

## Instructions

1. Inspect project configuration, package directories, metadata ownership, API versions, hooks, and current CLI pin.
2. Choose a scratch org or development sandbox based on feature fidelity, data need, namespace, and lifecycle constraints.
3. Create synthetic fixtures and local contract tests that require no live org or secret.
4. Run formatting, static analysis, unit tests, schema checks, and metadata dependency checks locally.
5. With approval, create or authenticate the development org and deploy only the bounded source set.
6. Run Apex, Flow, Lightning, and integration tests applicable to the change; capture aggregate results and IDs only.
7. Delete synthetic data, close or expire temporary orgs, revoke temporary access, and record reproducible commands.

## Approval Boundaries

Do not create orgs, enable features, deploy metadata, load data, or change remote configuration without Dev Hub, admin, and component-owner approval.

## Output

Return the environment decision, pinned toolchain, source and fixture map, local and org test results, cleanup receipt, and remaining fidelity gaps.

## Error Handling

| Condition | Response |
|---|---|
| Scratch-org feature does not match production | Use an approved sandbox or revise the definition; do not weaken production metadata. |
| Deployment reports missing dependencies | Add the dependency explicitly or reduce the source set before retrying. |
| Test data cannot be proven synthetic | Stop and replace it before local export or CI use. |

## Example

A redacted completion receipt might look like this:

```text
project=sfdx; target=scratch-org; fixtures=synthetic; static=pass; deploy=validated; apex=pass; cleanup=complete
```

## Resources

- [Salesforce DX development model](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_develop.htm)
- [Scratch org definition file](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm)

## Next Steps

Run the workflow first in the lowest-risk authorized org and preserve its redacted receipt. Schedule a review against the next Salesforce seasonal release and the customer change calendar.

Versions

The database has no other skills named salesforce-local-dev-loop.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 4fa9120bd492 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100onenote-local-dev-loop
    Create a repeatable local OneNote development loop using synthetic fixtures, mocks, and an explicitly approved delegated sandbox. Use when implementing or debugging without touching real notebooks. Trigger with "develop OneNote locally", "mock OneNote API", or "set up OneNote sandbox".
  • 100adobe-local-dev-loop
    Build a repeatable local loop for Adobe adapters using synthetic contracts before any remote Runtime or product call. Use when implementing or debugging locally. Trigger with "develop Adobe integration locally", "mock Adobe API", or "aio app dev".
  • 100salesforce-developer
    Use when building, modifying, or deploying any Salesforce platform solution — Apex classes, Lightning Web Components, SOQL queries, Flows, Metadata API deployments, scratch org configuration, Salesforce CLI automation, or Agentforce DX agent metadata. Invoke for any core…
  • 100cursor-local-dev-loop
    Optimize local development workflow with Cursor. Triggers on "cursor workflow", "cursor development loop", "cursor productivity", "cursor daily workflow". Use when working with cursor local dev loop functionality. Trigger with phrases like "cursor local dev loop", "cursor loop", "cursor".
  • 90salesforce-architecture
    Use for org-level Salesforce architecture work — capacity planning, security/sharing review, integration patterns, multi-org strategy, tech-debt assessment.
  • 100salesforce-safe-delivery
    Use when making ANY change to a Salesforce org with Claude Code (Apex, LWC, flows, metadata, data) — especially when a production org is involved. Enforces sandbox-first delivery, live-org verification, impact analysis, and explicit human approval for every production action.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.