dx-project-create

Installation
SKILL.md

Creating a New Salesforce Project

Walk the user through a wizard that scaffolds a new Salesforce DX project, relocates this session into the new project, connects it to an org, and configures it for development. Run each step in order, confirming with the user before any environment-changing action.

The plugin's MCP servers come from the installed plugin, not the project, so they stay available after the session relocates. There is no per-project .mcp.json to copy.

Step 1: Choose a Project Template

This skill scaffolds every template the CLI offers, including UI-bundle web apps (React, Angular, Vue), so creating a project never requires installing another plugin. Once the project exists, the experience-ui-bundle-* skills own building it out (pages, components, deploy).

Read the template set live from the CLI, never from a baked-in list, because Salesforce adds templates over time:

sf template generate project --help

Parse the -t, --template=<option> line's <options: a|b|c|…> list; those names are the authoritative set. Fallback, only if the live list cannot be read: standard, empty, analytics, agent, reactinternalapp, reactexternalapp, angularinternalapp, angularexternalapp. Vue (vueinternalapp) is left out of the fallback because stable CLI builds reject it; newer builds list it in the live parse. If the parse failed and the user wants Vue, say the template list could not be read and ask them to update the Salesforce CLI. UI-bundle templates are named <framework><audience>app; internal = employee-facing, already authenticated; external = customer/partner-facing with login, registration, and profile.

Intent shortcut first. Take it only when the request resolves to exactly one template in the live list. Otherwise use the picker; never guess. Resolve {template} directly when:

Installs
2.7K
GitHub Stars
1.2K
First Seen
Aug 5, 2026