commerce-b2b-open-code-components-integrate

Copy Salesforce B2B Commerce open source components into store site metadata.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill commerce-b2b-open-code-components-integrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commerce-b2b-open-code-components-integrate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/commerce-b2b-open-code-components-integrate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill commerce-b2b-open-code-components-integrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of bringing Salesforce B2B Commerce open source components into a store, so teams can make them available in Experience Builder without hand-copying files or guessing the right metadata paths.

Core Features & Use Cases

  • Repository Integration: Clones or reuses the official open source components repository and validates its expected structure.
  • Store Metadata Detection: Finds an existing B2B store site locally or retrieves one from a connected org when needed.
  • Component and Label Copying: Copies all component folders and label sets into the selected site metadata so they can be deployed together.
  • Use Case: A commerce developer wants to add the full set of open source storefront components to an existing B2B site and then deploy them for immediate use in Experience Builder.

Quick Start

Ask the skill to integrate the open source B2B Commerce components into your selected store site metadata.

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

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

FAQPage Schema
How do I add open source B2B Commerce components to an Experience Builder site?

To add open source B2B Commerce components to an Experience Builder site, this skill copies the component folders and label sets directly into your selected store's site metadata. It automates the file copying and prepares the metadata for immediate deployment.

How do I integrate LWC components into Salesforce B2B Commerce site metadata?

Integrating LWC components into Salesforce B2B Commerce site metadata involves cloning the open source repository, detecting the local site bundle, copying component files, and validating the package directory structure for deployment.

Do I need to clone the repository before adding B2B Commerce components to my store?

Yes, you need to clone the repository before adding B2B Commerce components to your store. The skill requires repository cloning or reusing an existing local clone to validate the expected component structure and copy the files.

Can I retrieve site metadata from a connected org if I don't have a local B2B store site?

Yes, you can retrieve site metadata from a connected org if a local B2B store site is not found. The skill detects existing local store sites or retrieves the necessary site bundle from your connected org.

What is the best way to synchronize store-level assets for B2B Commerce deployment?

The best way to synchronize store-level assets for B2B Commerce deployment is to automate the copying of component folders and label sets into the site metadata, ensuring all assets are packaged and validated together.

Why does adding open source LWC components manually fail in Experience Builder?

Adding open source LWC components manually often fails in Experience Builder due to incorrect metadata paths or missing label sets. This skill removes manual file copying and validates the package directory structure to prevent integration errors.