b2c-mrt
Deploy and manage Managed Runtime (MRT) storefronts using the b2c CLI. Use this skill whenever the user needs to deploy a PWA Kit bundle, manage MRT environments and projects, set environment variables, configure URL redirects, or manage organization connections — even if they just say "deploy my PWA" or "set up a staging environment".
What this skill does
# B2C MRT Skill Use the `b2c` CLI to manage Managed Runtime (MRT) projects, environments, bundles, and deployments for PWA Kit storefronts. > **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli mrt bundle deploy`). ## Command Structure ``` mrt ├── org - Organizations and B2C connections │ ├── member - Organization-level member management │ └── cert - Custom domain certificates ├── project - Project management │ ├── member - Team member management │ └── notification - Deployment notifications ├── env - Environment management (incl. clone) │ ├── var - Environment variables │ ├── redirect - URL redirects │ └── access-control - Access control headers ├── bundle - Bundle and deployment management (incl. delete) └── user - User profile and settings ``` ## Quick Examples ### Deploy a Bundle ```bash # Push local build to staging b2c mrt bundle deploy -p my-storefront -e staging # Push to production with release message b2c mrt bundle deploy -p my-storefront -e production -m "Release v1.0.0" # Deploy existing bundle by ID b2c mrt bundle deploy 12345 -p my-storefront -e production ``` ### Manage Environments ```bash # List environments b2c mrt env list -p my-storefront # Create a new environment b2c mrt env create qa -p my-storefront --name "QA Environment" # Clone an existing environment (-e is the source; positional arg is the new slug) b2c mrt env clone qa -p my-storefront -e staging --clone-redirects --clone-env-vars # Get environment details b2c mrt env get -p my-storefront -e production # Invalidate CDN cache b2c mrt env invalidate -p my-storefront -e production ``` ### Environment Variables ```bash # List variables b2c mrt env var list -p my-storefront -e production # Set variables b2c mrt env var set API_KEY=secret DEBUG=true -p my-storefront -e staging # Delete a variable b2c mrt env var delete OLD_VAR -p my-storefront -e production ``` ### View Deployment History ```bash # List bundles in project b2c mrt bundle list -p my-storefront # View deployment history for environment b2c mrt bundle history -p my-storefront -e production # Download a bundle artifact b2c mrt bundle download 12345 -p my-storefront # Delete one or more bundles (uses bulk-delete for >1) b2c mrt bundle delete 12345 -p my-storefront b2c mrt bundle delete 12345 12346 12347 -p my-storefront --force ``` ### Organization Members and Certificates Organization members are distinct from project members; they hold a role at the organization level. Custom-domain certificates are organization-scoped and referenced by `b2c mrt env create`/`update`/`clone` via `--certificate-id`. ```bash # List, add, update, remove organization members b2c mrt org member list --org my-org b2c mrt org member add [email protected] --org my-org --role member --view-all-projects b2c mrt org member update [email protected] --org my-org --no-cert-permission b2c mrt org member remove [email protected] --org my-org # Manage custom domain certificates b2c mrt org cert list --org my-org b2c mrt org cert create shop.example.com --org my-org # output includes the DNS validation record b2c mrt org cert get 123 --org my-org b2c mrt org cert restart-validation 123 --org my-org b2c mrt org cert delete 123 --org my-org ``` ### Project Management ```bash # List projects b2c mrt project list # Get project details b2c mrt project get -p my-storefront # List project members b2c mrt project member list -p my-storefront # Add a member b2c mrt project member add [email protected] -p my-storefront --role developer ``` ### URL Redirects ```bash # List redirects b2c mrt env redirect list -p my-storefront -e production # Create a redirect b2c mrt env redirect create -p my-storefront -e production \ --from "/old-path" --to "/new-path" # Clone redirects between environments b2c mrt env redirect clone -p my-storefront --source staging --target production ``` ## Configuration ### dw.json Configure MRT settings in your project's `dw.json`: ```json { "mrtProject": "my-storefront", "mrtEnvironment": "staging" } ``` ### Environment Variables ```bash export MRT_API_KEY=your-api-key export MRT_PROJECT=my-storefront export MRT_ENVIRONMENT=staging ``` ### ~/.mobify Config Store your API key in `~/.mobify`: ```json { "api_key": "your-mrt-api-key" } ``` ## Detailed References - [Project Commands](references/PROJECT-COMMANDS.md) - Projects, members, and notifications - [Environment Commands](references/ENVIRONMENT-COMMANDS.md) - Environments, variables, redirects - [Bundle Commands](references/BUNDLE-COMMANDS.md) - Deployments, history, downloads ### More Commands See `b2c mrt --help` for a full list of available commands and options.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.