commerce-b2b-open-code-components-replace

Replaces OOTB B2B Commerce component definitions with open source equivalents in site content.json files.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill commerce-b2b-open-code-components-replace-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commerce-b2b-open-code-components-replace
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/commerce-b2b-open-code-components-replace
Command: npx skills add https://github.com/padjei/SF_Build --skill commerce-b2b-open-code-components-replace-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Migrating a Salesforce B2B Commerce store from out-of-the-box components to open source components requires manually finding and editing every component definition across many site metadata content.json files, which is tedious and error-prone. ## Core Features & Use Cases - Site-wide scan and cross-reference: Finds all OOTB commerce_builder component definitions in sfdc_cms__view and sfdc_cms__themeLayout content.json files and matches them against an authoritative mapping table. - Safe, verified replacement: Replaces definitions with exact site: equivalents only after confirming the target component exists in the cloned open source repository, batching all edits into a single Read/Write pass per file. - Lookup-only and view-scoped modes: Reports OOTB to open code mappings without modifying files, or limits work to a specific view directory. - Use Case: You have a B2B store using commerce_builder:heading, cartBadge, and searchInput across five views. The skill scans the site, shows a selectable list of replaceable components, swaps the definitions, and reports skipped or unmapped components with a deployment command. ## Quick Start Ask the assistant to replace the OOTB commerce components in your store's site metadata with their open code equivalents.

Frequently Asked Questions about commerce-b2b-open-code-components-replace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I replace OOTB B2B Commerce components with open source versions?▼

Scan the store's site metadata content.json files for commerce_builder definitions, cross-reference them against the OOTB-to-open-code mapping, select the components to replace, and write the mapped site: definitions back. The skill automates this scan, selection, and batched replacement workflow.

How do I find the open code equivalent of a commerce_builder component?▼

Look up the component in the assets/ootb-to-open-code-mapping.json file, which maps each commerce_builder definition to its site: equivalent, such as commerce_builder:heading to site:productHeading. The skill supports a lookup-only mode that reports mappings without modifying any files.

Can I replace components in only one view of my B2B store?▼

Yes, view-scoped mode limits file discovery and reads to a specific sfdc_cms__view/<ViewName>/ directory instead of scanning all views. Provide the view name or path and only that scope is scanned and updated.

What happens if an OOTB component has no open source equivalent?▼

Components missing from the mapping table are reported as unmapped and left unchanged. Components with a mapping whose target is not found in the cloned open source repo are skipped and reported under a not-in-repo category.

What prerequisites are needed before replacing commerce components?▼

The open source components repository must be cloned at .tmp/b2b-commerce-open-source-components, the store's site metadata must be retrieved locally, and the open code components must be integrated into the store's site metadata. A companion integration skill verifies and completes these prerequisites.