salesforce-development

Plugin salesforce-development from marketplace salesforce in forcedotcom/sf-skills. Commands read from the repo's manifest — 6 days ago.

Skills (38)

• automation-flow-generate

  Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as \"when a record is created\", \"trigger dai

• dx-org-manage

  Use to EXECUTE Salesforce org operations immediately via the sf CLI (this skill runs them, it does NOT generate scripts): create scratch orgs (from edition, definition file, snapshot, or org shape), list/display/resume/delete scratch orgs, open orgs in browser. Trigger: 'create scratch org', 'create

• dx-project-create

  Scaffold a Salesforce DX project from any template (standard, agent, analytics, React/Angular/Vue app), move the session in, connect an org, enable source tracking. Use to create a Salesforce/SFDX project. DO NOT TRIGGER for: existing UI-bundle apps (experience-ui-bundle-frontend-generate); UI-bundl

• platform-apex-anonymous-run

  Runs anonymous Apex against the connected org (.apex file or pasted snippet), capturing the debug log, surfacing errors. Triggers on \"run this anonymous apex\", \"execute this script against my org\", \"what does this code return\", or \"execute scripts/foo.apex\". Wraps scripts in savepoint+rollba

• platform-apex-generate

  Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resourc

• platform-apex-logs-debug

  Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code

• platform-apex-test-generate

  Use to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debuggi

• platform-apex-test-run

  Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent te

• platform-capability-search

  Use this when someone says I don't know where to start or help me get going, asks where am I? in the six-stage journey, requests on-demand org feature detection for Data 360, OmniStudio, or DevOps Center, or asks what could help me do X / which plugin would help with X for a task no installed skill

• platform-custom-application-generate

  Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app contai

• platform-custom-field-generate

  Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values pe

• platform-custom-metadata-type-generate

  Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, __mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (conf

• platform-custom-object-generate

  Use when users create, generate, or validate Salesforce Custom Object metadata. Trigger on custom objects, .object files, sharing models, name fields, or validation rules — e.g. \"create a custom object\" — and deployment errors around sharing models and Master-Detail relationships. Also keep the ob

• platform-custom-report-type-generate

  Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors fo

• platform-custom-setting-generate

  Use to create, generate, or validate Salesforce Custom Setting metadata. Trigger on custom settings (hierarchy/list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags/toggles, kill switches, or admin on/off switches (e.g. bypass triggers during a data load); als

• platform-custom-tab-generate

  Use this skill when users need to create or configure Salesforce Custom Tabs. Trigger when users mention tabs, navigation tabs, object tabs, web tabs, Visualforce tabs, Lightning component tabs, app page tabs, or tab configuration. Also use when users want to add navigation to custom objects, create

• platform-data-and-tooling-api-context-get

  Authoritative field/schema reference for 2130 STANDARD Salesforce objects — sObject and Tooling field API names, types, properties (filterable/sortable/groupable/updateable), and relationships for Account, Contact, Opportunity, Lead, Case, ApexClass, and more. Load alongside a SOQL/Apex skill when f

• platform-data-manage

  Salesforce data operations with 130-point scoring. Use to create, update, delete, bulk import/export, generate test data, and clean up org records via sf CLI and anonymous Apex. TRIGGER on creating test data, bulk import/export, sf data CLI commands, data-factory patterns for Apex tests, or seeding/

• platform-destructive-deploy

  Execute the destructiveChanges.xml delete-and-deploy workflow against a Salesforce org. TRIGGER when the user asks to delete/remove a custom object, field, Apex class, flow, or any metadata component FROM an org, or to perform a 'destructive deploy' / removal as part of a release. Validates first an

• platform-environment-validate

  Validate and configure the local Salesforce development environment. Runs a prerequisite scan across required tools with per-tool status and offers to install or update missing items. Use when the user asks to 'check my setup', 'validate tools', 'verify prerequisites', 'am I set up correctly', or re

• platform-flexipage-generate

  Use when users create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger on RecordPage, AppPage, HomePage, Lightning pages, adding components to a page, page customization (e.g. 'customize the record page'), or .flexipage-meta.xml files (regions, components, deployment e

• platform-headless-360-integrate

  Read org state and change Setup through the Headless 360 (H360) MCP tools discover, describe, dispatch_readonly, and dispatch. Use when H360 tools are present and the answer is org state no skill or sf command reads: Setup settings, feature or license access, org-specific caps, health checks, releas

• platform-lightning-app-coordinate

  Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a \"complete app\", \"Lightning app\", \"business solution\", \"management system\", or describes a scenario requiring multiple interconnected Salesforce components (ob

• platform-list-view-generate

  Use this skill when users need to create, generate, or validate Salesforce List View metadata. Trigger when users mention list views, filtered record lists, creating views, setting up record columns, filtering records by criteria, or ask about list view visibility. Also use when users say things lik

• platform-lsp-integrate

  Reference/contract for the Salesforce LSP MCP tools and unavailability handling. Use when asking how to use the LSP, which tools exist, what apex.diagnostics / validate_soql / complete_soql do, why a tool errors with lsp_disabled, no_apex_workspace, or no_org_connected, or how to debug/disable it. D

• platform-manifest-generate

  Use to generate a package.xml (and optionally destructiveChanges.xml / Pre / Post) from a source dir, a component list, or org introspection. Trigger on 'generate a package.xml from this folder', 'create a manifest for these classes', 'I need a deploy manifest', or 'destructiveChanges.xml for deleti

• platform-metadata-api-context-get

  REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generator (if you load a generator, you ALSO load this). Use whenever you create, generate, edit, or author metadata or a *-meta.xml file (custom object, field, flow, and 604 M

• platform-metadata-deploy

  Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, validates a deploy or does a dry-run, deploys to a Production org, quick-deploys a validated job ID, ships/promotes to prod, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deploym

• platform-metadata-discovery-get

  Use before creating, changing, or writing code against Salesforce metadata, to find out what already exists in the org with the right tool. Routes each question to metadata grounding, scoped SOQL with sf data query, sf sobject list or describe, sf org list metadata, source retrieval, or local files,

• platform-metadata-grounding-get

  Find metadata that already exists in a Salesforce org by meaning, when you do not know its exact API name. Use to find objects, fields, flows, Apex classes, picklist values, permission sets, validation rules, record types, and sharing rules by what they store or do. Use before creating metadata to c

• platform-metadata-retrieve

  ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project with sf project retrieve start. Supports retrieval by all changes, source directory, metadata type (wildcards), manifest (package.xml), or package name, in source or metadata (ZIP) format. Use when the user asks to retrieve

• platform-permission-set-generate

  Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.

• platform-report-generate

  Use when users create, generate, or validate Salesforce Lightning Report metadata (.report-meta.xml) — tabular, summary, matrix, or joined reports with columns, groupings, filters, charts, cross-filters, buckets, formulas, or time-frame filters. Triggers on \"create a report\", \"build a report\", \

• platform-sharing-owd-configure

  Use when the user wants to retrieve or update Organization-Wide Default (OWD) sharing settings for Salesforce objects. TRIGGER on org-wide defaults, checking/viewing sharing defaults, changing default access levels (Private, Public Read Only, Public Read/Write, Controlled by Parent), internal/extern

• platform-sharing-rules-generate

  Use when users get, create, edit, delete, or retrieve Salesforce Sharing Rules metadata for record-level access. TRIGGER on sharing rules, record/criteria-based/role-based/guest-user sharing, sharingCriteriaRules/sharingOwnerRules/sharingGuestRules, .sharingRules-meta.xml files, or sharing records w

• platform-soql-query

  Use when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan/selectivity analysis, and performance or safety improvements. TRIGGER when the user writes, optimizes, or debugs SOQL/SOSL, touches .soql files, or asks abo

• platform-validation-rule-generate

  Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formu

• platform-value-set-generate

  Use to create, generate, or validate a Salesforce GlobalValueSet (reusable picklist shared across fields) or customize a StandardValueSet (built-in picklists like Industry, Lead Source, Opportunity Stage). Trigger on global/standard value set, reusable picklist, .globalValueSet-meta.xml or .standard

Slash commands (14)

• /salesforce-development:discover

  Show ranked what's-next nudges across the six-stage journey, run on-demand org feature detection, or find an uninstalled plugin that matches a specific task.

• /salesforce-development:feedback

  Record a quick 1-5 satisfaction rating as local usage telemetry. Manual-only — never dispatched by the model.

• /salesforce-development:login

  Authenticate to a new Salesforce org via the browser (sf org login web). Optionally set the org as the project's default target.

• /salesforce-development:logout

  Sign out of one or all Salesforce orgs (sf org logout). Confirms before destructive action.

• /salesforce-development:org

  Show just the connected Salesforce org details — alias, edition, API version, instance URL, username.

• /salesforce-development:plugin-install

  Confirm and install exactly one uninstalled plugin-catalog entry, or record an explicit decline.

• /salesforce-development:plugin-recommendations

  Turn uninstalled-plugin recommendations on or off, tune how readily they trigger, or show current status.

• /salesforce-development:project

  Show just the local SFDX project metadata stats — Apex/triggers/LWC/Aura/objects/perm sets/flows counts and git status.

• /salesforce-development:reset-source-tracking

  Reset source tracking for the target org — tells the CLI to forget all tracked changes so the next push/pull treats the full org as new state. Destructive on shared sandboxes. Requires explicit confirmation before executing.

• /salesforce-development:set-default

  Set the project's target-org (the org that all sf commands run against by default). If no org is named, lists the authenticated orgs for the user to pick.

• /salesforce-development:setup

  Validate the local Salesforce development environment — scan required tools (SF CLI, Code Analyzer, Node, NPM, Git, MCP, Source Tracking) with 🔴/🟡/🟢 status and offer guided install/update.

• /salesforce-development:status

  Show the Salesforce project banner — connected org, edition, API, project metadata stats, and MCP server status.

• /salesforce-development:telemetry

  Turn plugin usage telemetry on or off, or show its current status (what's collected, machine id, buffered events).

• /salesforce-development:welcome

  Display the Salesforce session banner — connected org, edition, API, project metadata stats, MCP servers. Auto-invoked at session start by the SessionStart hook.

Subagents (1)

• salesforce-dev

  Primary Salesforce development agent. Activates automatically in Salesforce projects (sfdx-project.json present). Routes requests through skills, then SF CLI, then direct API as a last resort.

MCP servers (4)

• salesforce-metadata-experts

  runs: node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-mcp-proxy.bundled.js metadata-experts

• salesforce-metadata-grounding

  runs: node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-mcp-proxy.bundled.js metadata-grounding

• salesforce-headless-360

  runs: node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-headless-360-optin.js ${CLAUDE_PLUGIN_ROOT}/scripts/sf-mcp-proxy.bundled.js headless-360

• salesforce-lsp

  runs: node ${CLAUDE_PLUGIN_ROOT}/bin/sf-lsp-host.bundled.js

Hooks (30)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context detect

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context telemetry-capture session_start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context cli-update-notice

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context verify-org

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context verify-org

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate prod-check

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate prod-check

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate destructive

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/bin/lsp-precheck

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/bin/lsp-precheck

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context scaffold-gate

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context scaffold-gate

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context skills-first-advisory

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context record-skill-dispatch

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context telemetry-capture skill_dispatched

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context telemetry-capture agent_dispatched

• UserPromptSubmit

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context prompt-dispatch

• UserPromptExpansion

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context prompt-dispatch

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context post-bash

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate auto-deploy

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate auto-deploy

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-deploy-gate auto-deploy

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/sf-context resolution-trace

Similar plugins