Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

b2c-setup

/b2c-setup

Planuje i przeprowadza konfigurację sandboxa B2C Commerce: dane przykładowe, witryny, indeksy i replikację, z potwierdzeniem przed zmianami.

Licencja
Apache-2.0
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
7
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Planuje i przeprowadza konfigurację sandboxa B2C Commerce: dane przykładowe, witryny, indeksy i replikację, z potwierdzeniem przed zmianami.

Wyzwalacze z opisu

set up my new realmget Market Street running on my sandbox
Oryginalny opis (EN)

Plan and run end-to-end setup of a B2C Commerce sandbox or realm (staging, production, development) with the b2c CLI — sample storefront data, sites, search indexes, code, Storefront Next storefronts, and replication — with confirmation before changes to shared instances. Use this skill whenever the user wants to set up a new sandbox or realm, load demo or sample data, stand up a storefront on a fresh instance, or get production ready from staging — even if they just say "set up my new realm" or "get Market Street running on my sandbox". For CLI connection settings alone, use b2c-cli:b2c-confi

Jak działa

  1. Safety First
  2. Choose a Path
  3. Workflow Catalog
  4. Related Skills
Sekcje z nagłówków SKILL.md, w oryginale · 65 linii, 656 słów
Podgląd SKILL.md
---
name: b2c-setup
description: Plan and run end-to-end setup of a B2C Commerce sandbox or realm (staging, production, development) with the b2c CLI — sample storefront data, sites, search indexes, code, Storefront Next storefronts, and replication — with confirmation before changes to shared instances. Use this skill whenever the user wants to set up a new sandbox or realm, load demo or sample data, stand up a storefront on a fresh instance, or get production ready from staging — even if they just say "set up my new realm" or "get Market Street running on my sandbox". For CLI connection settings alone, use b2c-cli:b2c-config.
---

# B2C Setup Skill

Set up a B2C Commerce sandbox or realm from an empty instance to a working storefront. This skill is an index: pick the path for the target, follow its reference, and use the workflow catalog for product- or feature-specific steps.

> **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (for example, `npx @salesforce/b2c-cli sites list`).

## Safety First

Classify every target before changing it. Staging, production, and development instances are shared and can serve live traffic; imports and replication there change global settings for every site on the instance.

| Target                                     | Before each change                                                                                                     |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| Sandbox                                    | Confirm creating (billable) or deleting a sandbox. Imports and storefront setup can proceed once the user asked.       |
| Staging, production, development instances | State the instance hostname and the exact change, then wait for explicit approval. Ask again for each separate change. |
| Account Manager (API clients, users, roles) | Show every detail (organization, roles, tenant filter, scopes) and wait for explicit approval. Ask again for each client. |

- Never infer that a target is a sandbox from a configuration name; check the hostname (see [safety](references/SAFETY.md)).
- Approval for one instance or step does not carry to the next.
- Production and development receive code and data by replication from staging. Do not import site data there directly; the storefront record is the exception (see `b2c-cli:b2c-storefronts`).

Recommend Safety Mode for shared instances: [safety](references/SAFETY.md).

## Choose a Path

| Goal                                                      | Path                                                   |
| --------------------------------------------------------- | ------------------------------------------------------ |
| A development sandbox with sample data and a storefront   | [Sandbox setup](references/SANDBOX.md)                 |
| A new realm: staging first, then production / development | [Realm setup](references/REALM.md)                     |
| Sample sites, catalogs, and content for any instance      | [Storefront datasets](references/DATASETS.md)          |
| A Storefront Next storefront, project code, and `.env`    | [Storefront Next setup](references/STOREFRONT-NEXT.md) |
| Add an instance to an existing Storefront Next project    | `b2c-cli:b2c-storefronts`                              |

Every path starts the same way:

1. **Connect.** Configure the instance and API client, then check with `b2c setup inspect`. See `b2c-cli:b2c-config`. Jobs, sites, and storefront commands need an API client; if the user has none, create one with their sign-in (`b2c-cli:b2c-am`, Create Client), and only after they approve every detail of it. Creating a Storefront Next storefront from the CLI needs storefront scopes on the client: [Storefront Next setup](references/STOREFRONT-NEXT.md#1-api-client-for-the-cli).
2. **Check what exists.** `b2c sites list` and `b2c code list` show existing sites and code versions. Do not overwrite existing sites or settings without approval.
3. **Load data** (staging or sandbox only), then **rebuild search indexes**.
4. **Deploy code** for the storefront type (cartridges, or a Storefront Next storefront).
5. **Verify** each step before starting the next.

## Workflow Catalog

Steps that depend on the product line, license, or feature. Use only the rows that apply to the user's realm.

| Workflow                                   | Applies to                                 | Guidance                                                                                             |
| ------------------------------------------ | ------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| Instance connection, API clients, roles    | All                                        | `b2c-cli:b2c-config`, `b2c-cli:b2c-am`, `b2c-cli:b2c-bm-users-roles`                                 |
| Sample data and search indexes             | All                                        | [Storefront datasets](references/DATASETS.md), `b2c-cli:b2c-job`                                     |
| Site archives and custom data              | All                                        | `b2c-cli:b2c-site-import-export`                                                                     |
| Code and data replication                  | Realms (staging to production/development) | `b2c-cli:b2c-replication`                                                                            |
| Storefront Next storefront and MRT project | Storefront Next                            | [Storefront Next setup](references/STOREFRONT-NEXT.md), `b2c-cli:b2c-storefronts`, `b2c-cli:b2c-mrt` |
| Cartridge storefronts (SFRA)               | Cartridge-based storefronts                | `b2c-cli:b2c-code`, `b2c-cli:b2c-sites`                                                              |
| Shopper authentication (SLAS)              | Headless and composable storefronts        | `b2c-cli:b2c-slas`                                                                                   |
| Commerce apps                              | Commerce apps                              | `b2c-cli:b2c-cap`                                                                                    |
| eCDN zones and certificates                | Storefronts on eCDN                        | `b2c-cli:b2c-ecdn`                                                                                   |

## Related Skills

- [Realm Setup guide](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/realm-setup.md) (`b2c docs read guide-realm-setup`) — the user-facing version of this skill
- `b2c-cli:b2c-sandbox` — create, start, stop, and clone sandboxes
- `b2c-cli:b2c-storefronts` — create or import Storefront Next storefronts
- `b2c-cli:b2c-replication` — replication jobs for staging
- `b2c-ops:b2c-production-triage` — investigate problems after launch
Pliki w paczce (7)
  • SKILL.md 7 KB
  • evals/trigger-evals.json 1 KB
  • references/DATASETS.md 4 KB
  • references/REALM.md 6 KB
  • references/SAFETY.md 2 KB
  • references/SANDBOX.md 2 KB
  • references/STOREFRONT-NEXT.md 10 KB

Wersje

W bazie nie ma innych skilli o nazwie b2c-setup.

Migawka bazy z 13.11.2026 · wersja paczki aa1f0ee775ab (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100b2c-storefronts
    Przenosi witryny Storefront Next między instancjami B2C Commerce przez CLI b2c, z eksportem, importem i konfiguracją projektu.
  • 100b2c-replication
    Automatyzuje replikację kodu i danych z instancji staging B2C Commerce na produkcję lub dev przez zadanie CLI b2c.
  • 98windows-sandbox-setup
    Przygotowuje Windows Sandbox do pracy z narzędziami sandbox-mcp i sbx, także wtedy, gdy działający sandbox blokuje start nowego.
  • 82realm-load-harness
    Uruchamia i interpretuje test obciążeniowy serwera realm: równoległe zapytania i zapisy oraz czasy odpowiedzi.
  • 84realm-sync
    Przenosi pliki między dyskiem a realmem Boxel: wysyła zmiany, pobiera realm, synchronizuje dwukierunkowo i listuje realmy.
  • 100salesforce-multi-env-setup
    Buduje środowiska Salesforce, od development i scratch orgów po sandbox, staging i produkcję, z jawną promocją zmian i kontrolą dryfu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.