SalesforceCommerceCloud/b2c-developer-tooling

B2C CLI, VSCode Extension, Skills+MCP, and Tooling SDK for Salesforce Agentforce Commerce B2C

This repository also configures its own agents. See what b2c-developer-tooling tells them →

56Stars on the repository
96Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
Apache-2.0Licence, which decides whether bodies are shown

b2c-scaffold

01

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex needs its repo

Generate B2C Commerce cartridges, controllers, hooks, custom APIs, job steps, and Page Designer components from scaffold templates. Use this skill whenever the user needs to create a new cartridge, add a controller or hook to an existing cartridge, bootstrap a custom API endpoint, or generate boilerplate for job steps…

not rated 56 yesterday A SkillSpector: warn 92 tokens original Apache-2.0

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Convert a Figma frame into merchant-authorable Storefront Next Page Designer blocks: splits the frame into sections, proposes attributes with defaults from the design copy, reconciles brand tokens, writes React components with @Component/@AttributeDefinition metadata, a required fallback and (for catalog sections) a…

not rated 56 changed 13d ago A SkillSpector: warn 181 tokens original Apache-2.0

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Build or sync a Storefront Next vertical's Figma design kit — duplicate the official kit, update Brand variable collections from brand.css, edit components at the correct layer, and publish Figma Code Connect mappings. Use when asked to set up, duplicate, or sync a Figma kit, update Figma brand variables, or keep…

not rated 56 changed 13d ago A SkillSpector: warn 87 tokens original Apache-2.0

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Consuming the salesforce-b2c-tooling-sdk Python SDK from scripts or Jupyter notebooks — installation, choosing an authentication mechanism, and the available OCAPI/SCAPI/WebDAV clients and operations. Use when writing Python (or notebook) code that authenticates to a B2C Commerce instance, resolves config from…

not rated 56 yesterday A 103 tokens original Apache-2.0

b2c-mcp-cip

05

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Required before cipquery. Discover and run CIP reports or analytics SQL for sales, merchandising, and technical operations; resolve warehouse access, bound results, and interpret site/date scope.

not rated 56 yesterday A 43 tokens original Apache-2.0

b2c-mcp-config

06

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Resolve B2C MCP configuration, authentication, and external access grants with masked inspection. Use for setup, credential, or wrong-target issues; routine configinspect needs no skill read.

not rated 56 yesterday A 44 tokens original Apache-2.0

b2c-mcp-debugger

07

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Debug B2C Commerce server-side scripts with the MCP debugger tools, using bounded breakpoint capture, request triggering, state inspection, and reliable session cleanup.

not rated 56 yesterday A 38 tokens original Apache-2.0

b2c-mcp-scapi

08

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Required before scapisearch or scapiexecute. Discover standard and live custom SCAPI contracts, compose Admin and Shopper requests, and verify changes under configured authentication and Safety Mode.

not rated 56 changed 10d ago A 43 tokens original Apache-2.0

b2c-mcp-server

09

SalesforceCommerceCloud/b2c-developer-tooling

Skill Claude CodeCodex

Index and setup for the B2C Commerce MCP server, covering toolset selection, tool choice by task, and the skill catalog. Use to enable tools, pick the right tool, or find the skill that covers a B2C task.

not rated 56 changed 10d ago B 56 tokens original Apache-2.0

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: