From b2c
Guides new developers through first-time Salesforce B2C Commerce setup: CLI install, sandbox connection, and first cartridge deploy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b2c:b2c-onboardingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide a new developer through a first-time B2C Commerce setup, from CLI install to first cartridge deploy. Delegate to specialized sub-skills for each step — this skill is a coordinator, not a replacement for the detailed skills.
Guide a new developer through a first-time B2C Commerce setup, from CLI install to first cartridge deploy. Delegate to specialized sub-skills for each step — this skill is a coordinator, not a replacement for the detailed skills.
dw.json without confirmation.Silently identify the IDE from system context:
| Signal | Client |
|---|---|
| "Claude Code" | claude-code |
| "Cursor" | cursor |
| "VS Code" / "Visual Studio Code" | vscode |
| "Codex" | codex |
| "Gemini CLI" | gemini-cli |
| Unrecognized | other |
This onboarding skill is part of the b2c plugin. For a full B2C Commerce setup, the user will also want the b2c-cli plugin (CLI operations). Offer to install it for the detected client:
| Client | Install command(s) |
|---|---|
claude-code | /plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling then /plugin install b2c-cli@b2c-developer-tooling (and optionally /plugin install b2c-dx-mcp@b2c-developer-tooling for the MCP server — Claude Code only) |
vscode (GitHub Copilot) | Command Palette (Cmd+Shift+P) → Chat: Install Plugin From Source → enter the repo SalesforceCommerceCloud/b2c-developer-tooling |
| GitHub Copilot CLI | copilot plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling then copilot plugin install b2c-cli@b2c-developer-tooling |
cursor | Cursor Settings → Plugins → add marketplace URL https://github.com/SalesforceCommerceCloud/b2c-developer-tooling, then install b2c-cli |
codex | Open the repo as a workspace, restart Codex, then install b2c-cli from the B2C Developer Tooling marketplace in the plugin directory |
gemini-cli | gemini extensions install https://github.com/SalesforceCommerceCloud/b2c-developer-tooling (run in terminal, not inside the CLI) |
other | Use the file-copy installer below |
For clients other than Claude Code, the b2c-dx-mcp MCP server can be installed directly — see the MCP installation docs.
Alternative — file-copy installer for any IDE (also the right command to update already-installed skills or add a specific skill set):
# Interactive: select skill sets and IDEs
b2c setup skills
# Install a specific skill set to a specific IDE
b2c setup skills b2c-cli --ide cursor
b2c setup skills b2c --ide vscode
# Update existing skills to the latest release
b2c setup skills b2c-cli --ide cursor --update
b2c setup skills b2c --ide cursor --update
# Install globally (all projects)
b2c setup skills b2c-cli --ide cursor --global
If the user already has some skills installed and is asking how to upgrade, point them at b2c setup skills <set> --ide <ide> --update.
Run b2c --version. If the command is not found:
npx @salesforce/b2c-cli <command>.npm install -g @salesforce/b2c-cli (or the pnpm / yarn equivalent).Do not block on the global install — npx is sufficient for the rest of this flow.
B2C Commerce has no self-service signup. The user must have Account Manager access provisioned by their organization's B2C Commerce admin before any of the following steps will work.
Ask (if not already clear from context): "Do you have a Salesforce B2C Commerce Account Manager login and a target instance (sandbox or PIG)?"
Run b2c setup inspect to see whether a dw.json or credentials are already configured.
For deep troubleshooting (wrong instance, profile switching, token inspection), delegate to the b2c-config skill.
Guide the user to create a dw.json in the project root:
b2c setup
This prompts for hostname, client ID/secret (or username/password), and code version. For deeper configuration topics (multiple profiles, env vars, cert-based auth), delegate to the b2c-config skill.
If the user wants to work against an existing sandbox, confirm it is reachable:
b2c setup inspect
b2c sandbox list # requires API access
If the user needs a fresh sandbox, delegate to the b2c-sandbox skill for the full create flow. Only create a sandbox when explicitly asked.
If the user has cartridges locally:
b2c code deploy
For selective deploys, watch mode, or reload, delegate to the b2c-code skill.
If the user does not yet have cartridges, point them at the canonical starting points:
b2c-mrt skill on request.Once setup is working, ask a single directing question to hand off to the right skill:
"What do you want to work on first?
- Build or modify a storefront (SFRA cartridges, ISML, controllers)
- Build a Custom API (SCAPI)
- Operate an existing instance (deploy, run jobs, tail logs, manage sites)
Or if you have something else in mind, tell me."
Route by the answer:
b2c-controllers, b2c-isml, b2c-forms, b2c-hooksb2c-custom-api-development, b2c-scapi-admin, b2c-scapi-shopperb2c-code, b2c-job, b2c-logs, b2c-sitesnpx claudepluginhub salesforcecommercecloud/b2c-developer-tooling --plugin b2cSets up Salesforce Commerce dev environment with sfcc-ci CLI for B2C, sf CLI for B2B, Business Manager access, sandbox management, dw.json/.sfdx config, and SFRA/PWA Kit/Lightning project structures. Use for new projects.
Manages B2C Commerce cartridge code via deploy, download, activate, and watch commands. Useful for pushing code to sandboxes, pulling code, and setting up dev workflows with live reload.
Creates a Commerce B2B Store in Salesforce and retrieves auto-generated storefront metadata via an interactive 7-step workflow.