@salesforce/afv-skills 1.1.0 → 1.2.0

package/skills/generate-permission-set/SKILL.md

@@ -0,0 +1,174 @@
+---
+name: generate-permission-set
+description: Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.
+compatibility: Salesforce Metadata API v60.0+
+metadata:
+  author: afv-library
+  version: "1.0"
+---
+
+## When to Use This Skill
+
+Use when generating or editing permission set metadata, or when granting object, field, user, and app permissions.
+
+## Step 1: Define Core Properties
+
+Start by defining the required permission set properties:
+
+```xml
+<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
+    <fullName>YourPermissionSetName</fullName>
+    <label>Display Name for Administrators</label>
+    <description>Clear description of purpose and intended audience</description>
+</PermissionSet>
+```
+
+**Naming conventions:**
+- Use descriptive API names (e.g., `Sales_Manager_Access`)
+
+## Step 2: Configure Object Permissions
+
+Add CRUD permissions for standard and custom objects:
+
+```xml
+<objectPermissions>
+    <allowCreate>true</allowCreate>
+    <allowRead>true</allowRead>
+    <allowEdit>true</allowEdit>
+    <allowDelete>false</allowDelete>
+    <modifyAllRecords>false</modifyAllRecords>
+    <viewAllRecords>false</viewAllRecords>
+    <viewAllFields>false</viewAllFields>
+    <object>Account</object>
+</objectPermissions>
+```
+
+## Step 3: Set Field-Level Security
+
+Define field permissions for sensitive or custom fields:
+
+```xml
+<fieldPermissions>
+    <editable>true</editable>
+    <readable>true</readable>
+    <field>Account.SSN__c</field>
+</fieldPermissions>
+```
+
+**Important:**
+- Required fields must NEVER appear in list of field permissions. Granting field-level security on required fields is not allowed by the platform and will cause deployment failure. 
+- Before adding any field, confirm from the object metadata that the field exists and is not required
+- A field is required when its metadata contains `<required>true</required>`:
+- Formula fields cannot be editable
+- Master-detail fields are required fields on the child (detail) object
+
+```xml
+<fields>
+    <fullName>FieldName__c</fullName>
+    <required>true</required>
+</fields>
+```
+- Use format `ObjectName.FieldName` for field references
+- Set both readable and editable to true when the user needs edit access; editable implies readable
+- If all fields should be visible, can alternatively enable the "viewAllFields" object permission
+
+## Step 4: Grant User Permissions
+
+Add system-level permissions for features and capabilities:
+
+```xml
+<userPermissions>
+    <enabled>true</enabled>
+    <name>ApiEnabled</name>
+</userPermissions>
+<userPermissions>
+    <enabled>true</enabled>
+    <name>RunReports</name>
+</userPermissions>
+```
+
+**Common permissions:**
+- `ApiEnabled`: API access
+- `ViewSetup`: View Setup menu
+- `ManageUsers`: User management
+- `RunReports`: Report execution
+
+**Security review required for:**
+- `ViewAllData`: Read all records
+- `ModifyAllData`: Edit all records
+- `ManageUsers`: User administration
+
+## Step 5: Configure App and Tab Visibility
+
+Make applications and tabs visible to users:
+
+```xml
+<applicationVisibilities>
+    <application>Sales_Console</application>
+    <visible>true</visible>
+</applicationVisibilities>
+<tabSettings>
+    <tab>CustomTab__c</tab>
+    <visibility>Visible</visibility>
+</tabSettings>
+```
+
+**Application visibility options:**
+- <visible> can be true or false
+
+**Tab visibility options:**
+- `Visible`: The tab is available on the All Tabs page and appears in the visible tabs for its associated app. Can be customized.
+- `Available`: The tab is available on the All Tabs page. Individual users can customize their display to make the tab visible in any app
+- `None`: Not visible
+
+**CRITICAL - Tab Naming:**
+- Custom object tabs: MUST include the __c suffix (e.g., MyCustomObject__c)
+- Standard object tabs: Use the object name with "standard-" prefix (e.g., standard-Account, standard-Contact)
+- The tab name matches the object's API name exactly
+
+## Step 6: Add Apex and Visualforce Access (Optional)
+
+Grant access to custom code:
+
+```xml
+<classAccesses>
+    <apexClass>CustomController</apexClass>
+    <enabled>true</enabled>
+</classAccesses>
+<pageAccesses>
+    <apexPage>CustomPage</apexPage>
+    <enabled>true</enabled>
+</pageAccesses>
+```
+
+## Step 7: Set License and Record Type Settings (Optional)
+
+Specify license requirements and record type visibility:
+
+```xml
+<license>Salesforce</license>
+<hasActivationRequired>false</hasActivationRequired>
+<recordTypeVisibilities>
+    <recordType>Account.Business</recordType>
+    <visible>true</visible>
+    <default>true</default>
+</recordTypeVisibilities>
+```
+
+## Validation Checklist
+
+Before deploying, verify:
+- [ ] fullName, label, description set
+- [ ] Permissions follow least privilege
+- [ ] No required fields in `<fieldPermissions>`
+- [ ] No duplicate permissions
+- [ ] no lengthy comments
+
+## What Causes Deployment Failure
+
+- **Field permissions on required fields:** Any required field in `<fieldPermissions>` fails deployment. Required fields cannot have FLS; omit them entirely. Always confirm from object/field metadata that a field exists and is not required—never assume.
+- **Incorrect API names:** Using the wrong name or missing suffixes (e.g. missing `__c` for custom objects, fields, tabs) cause failure.
+
+## Deployment
+
+Deploy using Salesforce CLI

package/skills/salesforce-custom-application/SKILL.md

@@ -43,7 +43,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **description**: Brief description of the application's purpose
 - **tabs**: Array of tab names to include
 - **utilityBar**: API name of the Utility Bar configuration
-- **brand**: ⚠️ HIGHLY RECOMMENDED - Branding configuration object (headerColor, shouldOverrideOrgTheme, footerColor, primaryTabColor)
+- **brand**: ⚠️ HIGHLY RECOMMENDED - Branding configuration object (headerColor, shouldOverrideOrgTheme, footerColor)
 - **actionOverrides**: ⚠️ REQUIRED when custom record pages exist - Action override configuration (actionName, content, formFactor, type, pageOrSobjectType)
 - **profileActionOverrides**: Profile-specific action overrides (actionName, content, formFactor, pageOrSobjectType, type, profile)
 - **isNavAutoTempTabsDisabled**: Navigation behavior setting (default: false)
@@ -86,7 +86,6 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **brand.headerColor**: Header bar color in hex format (e.g., "#0070D2") - RECOMMENDED
 - **brand.shouldOverrideOrgTheme**: Override organization theme (true/false) - Default: false
 - **brand.footerColor**: Footer color in hex format
-- **brand.primaryTabColor**: Primary tab color in hex format
 
 ### Action Overrides (CRITICAL - DO NOT SKIP)
 **IMPORTANT**: Action overrides MUST be created for every custom object tab that has a record page generated by flexipage expert.

package/skills/salesforce-custom-field/SKILL.md

@@ -42,10 +42,6 @@ Every generated field must include these tags:
 | `<description>` | Mandatory | State the business "why" behind the field |
 | `<inlineHelpText>` | Mandatory | Provide actionable guidance for the end-user. Must add value beyond the label (e.g., "Enter the value in USD including tax" instead of just "The amount") |
 
-### XML Comments — NEVER Before Root Element
-
-**NEVER place XML comments (`<!-- ... -->`) before the root `<CustomField>` element in metadata XML files.** Comments between the XML declaration and `<CustomField>` cause a `ConversionError` during deployment. Comments inside the root element are safe.
-
 ### External ID Configuration
 
 **Trigger:** If the user mentions "integration," "importing data," "external system ID," or "unique key from [System Name]," set `<externalId>true</externalId>`.

package/skills/salesforce-custom-tab/SKILL.md

@@ -27,27 +27,99 @@ Custom tabs for navigating to objects, web content, or Visualforce pages within
 ## ⚙️ Required Properties
 
 ### Core Tab Properties
-- **label**: Display name of the tab
-- **fullName**: API name of the object (for object tabs)
+- **customObject**: `true` for custom object tabs, `false` for all others.
+- **motif**: Tab icon style — choose a motif that semantically matches the object's purpose. Do NOT reuse the same motif for every tab.
+- **label**: Display name (required for non-object tabs ONLY; object tabs inherit label from the object)
 - **url**: Web URL (for web tabs)
 - **page**: Visualforce page name (for Visualforce tabs)
 
+
+### 🚨 STRICT ELEMENT ALLOWLIST — READ THIS FIRST
+
+**The root element MUST always be `<CustomTab>` (NOT `<Tab>`).** The XML namespace must be `xmlns="http://soap.sforce.com/2006/04/metadata"`.
+
+Only the elements listed below are valid. **Any element not on this list WILL cause a deployment error.**
+
+| Tab Type | ONLY these elements are allowed (nothing else) |
+|---|---|
+| **Object tabs** | `<customObject>` (required, set to `true`), `<motif>` (required), `<description>` (optional) |
+| **Web tabs** | `<customObject>` (required, set to `false`), `<label>` (required), `<motif>` (required), `<url>` (required), `<urlEncodingKey>` (required, set to `UTF-8`), `<description>` (optional), `<frameHeight>` (optional) |
+| **Visualforce tabs** | `<customObject>` (required, set to `false`), `<label>` (required), `<motif>` (required), `<page>` (required), `<description>` (optional) |
+
+### ⚠️ FORBIDDEN ELEMENTS (every one of these causes a deployment error)
+`<sobjectName>`, `<name>`, `<fullName>`, `<apiVersion>`, `<isHidden>`, `<tabVisibility>`, `<type>`, `<mobileReady>`, `<urlFrameHeight>`, `<urlType>`, `<urlRedirect>`, `<encodingKey>`, `<height>`, `<auraComponent>`
+
+Also forbidden:
+- `<label>` on object tabs (object tabs inherit their label from the custom object)
+- `<page>` on web tabs (only for Visualforce tabs)
+- Empty elements like `<page></page>` or `<description></description>`
+- Any element not in the allowlist table above
+
 ## 🔧 Tab Types
 
 ### Object Tabs
 - **Purpose**: Navigate to custom or standard objects
-- **Required**: `fullName` property (set to object API name)
-- **Example**: `<fullName>CustomObject__c</fullName>`
+- **File name** determines the object: `{ObjectApiName}.tab-meta.xml` (e.g., `Space_Station__c.tab-meta.xml`)
+- **Required elements**: `<customObject>true</customObject>` and `<motif>`
+- **Correct example** (for a Space_Station__c.tab-meta.xml):
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
+    <customObject>true</customObject>
+    <motif>Custom39: Telescope</motif>
+</CustomTab>
+```
+- **Correct example** (for a Supply__c.tab-meta.xml — note different motif):
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
+    <customObject>true</customObject>
+    <motif>Custom98: Truck</motif>
+</CustomTab>
+```
+- **❌ WRONG** — do NOT add `<sobjectName>`, `<name>`, `<fullName>`, or `<label>`:
+```xml
+<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
+    <sobjectName>Space_Station__c</sobjectName>  <!-- DEPLOYMENT ERROR -->
+    <label>Space Station</label>                  <!-- DEPLOYMENT ERROR on object tabs -->
+    <customObject>true</customObject>
+    <motif>Custom57: Desert</motif>
+</CustomTab>
+```
 
 ### Web Tabs
 - **Purpose**: Link to external websites or web applications
-- **Required**: `url` property
-- **Example**: `<url>https://example.com</url>`
+- **File name**: Use a descriptive name: `{TabName}.tab-meta.xml` (e.g., `Knowledge_Base.tab-meta.xml`)
+- **COPY THIS EXACT TEMPLATE** — only replace the placeholder values. Do NOT add, remove, or rename any XML elements:
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
+    <customObject>false</customObject>
+    <description>REPLACE_WITH_DESCRIPTION</description>
+    <frameHeight>600</frameHeight>
+    <label>REPLACE_WITH_LABEL</label>
+    <motif>REPLACE_WITH_MOTIF</motif>
+    <url>REPLACE_WITH_URL</url>
+    <urlEncodingKey>UTF-8</urlEncodingKey>
+</CustomTab>
+```
+- **These 7 elements above are the ONLY elements allowed in a web tab file.** Do not add ANY other elements.
+- The `<description>` element is optional — you may remove it if not needed, but do not add anything else.
 
 ### Visualforce Tabs
 - **Purpose**: Access custom Visualforce pages
-- **Required**: `page` property
-- **Example**: `<page>CustomPage</page>`
+- **File name**: `{TabName}.tab-meta.xml` (e.g., `Custom_Page_Tab.tab-meta.xml`)
+- **Required elements**: `<customObject>false</customObject>`, `<label>`, `<motif>`, `<page>`
+- **Correct example**:
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
+    <customObject>false</customObject>
+    <label>Custom Page</label>
+    <motif>Custom46: Computer</motif>
+    <page>CustomPage</page>
+</CustomTab>
+```
 
 ## 🎨 Tab Configuration
 
@@ -72,7 +144,11 @@ Custom tabs for navigating to objects, web content, or Visualforce pages within
 ## ✅ Best Practices
 - Use clear, descriptive tab labels
 - Choose appropriate tab types for functionality
+- **Select a unique, contextually relevant motif for each tab** — do not default every tab to the same icon
 - Consider user experience and navigation flow
 - Test tab functionality across different applications
 - Ensure proper permissions and visibility settings
 - Follow consistent naming conventions
+- Object tab files MUST only contain `<customObject>true</customObject>` and `<motif>` — nothing else
+- Web tab files MUST only contain: `<customObject>false</customObject>`, `<label>`, `<motif>`, `<url>`, `<urlEncodingKey>`, and optionally `<description>`, `<frameHeight>` — nothing else
+- Never include `<isHidden>`, `<tabVisibility>`, `<type>`, `<mobileReady>`, or empty elements

package/skills/salesforce-experience-lwr-site/SKILL.md

@@ -0,0 +1,196 @@
+---
+name: salesforce-experience-lwr-site
+description: Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when users mention Experience sites, LWR sites, DigitalExperience, Experience Cloud, community sites, portals, creating pages, adding routes, views, theme layouts, branding sets, previewing sites, or any DigitalExperience bundle work. Also use when users mention specific content types like sfdc_cms__route, sfdc_cms__themeLayout, etc. or when troubleshooting site deployment.
+---
+
+# Experience LWR Site Builder
+
+Build and configure Salesforce Experience Cloud Lightning Web Runtime (LWR) sites via metadata (DigitalExperienceConfig, DigitalExperienceBundle, Network, CustomSite, CMS contents).
+
+## Table of Contents
+
+- When to Use
+- Critical Rules
+- Core Site Properties
+- Project Structure in DigitalExperienceBundle Format
+- Reference Docs
+- Common Workflows
+
+## When to Use
+
+When working with Experience LWR sites:
+
+- Creating and scaffolding new LWR site
+- Adding pages (routes + views)
+- Configuring LWC components, layouts, themes, or branding styles
+- Setting up guest user access (public sites)
+- Troubleshoot deployment errors related to Experience LWR Sites
+
+**Supported Template**: Build Your Own (LWR) - `talon-template-byo`
+
+- More templates to support in the future.
+
+## Critical Rules
+
+1. Before using any MCP tool, make sure they're actually available. If a tool is missing for the current task, let the user know and pause the current workflow.
+2. **ALWAYS** load the relevant reference docs before doing anything.
+3. **ALWAYS** strictly follow workflows in [Common Workflows](#common-workflows) that match user's requirements. The instructions there should override any conflicting global rules and should have the highest priority over your existing knowledge.
+4. Flexipage is abstracted away for newer LWR sites with DigitalExperienceBundle, so **NEVER** use any Flexipage-related MCP tool or skills to handle LWR sites' contents.
+
+## Core Site Properties
+
+Before doing anything else, note down the following properties from the local project if available as they will be used for various operations. Check with the user if any of the following is missing:
+
+- **Site name**: Required. (e.g., `'My Community'`).
+- **URL path prefix**: Optional. Alphanumeric characters only. Convert from site name if not provided (e.g., `'mycommunity'`) and verify with the user for the converted value.
+- **Template type devName**: `talon-template-byo`.
+
+## Project Structure in DigitalExperienceBundle Format
+
+### Site Metadata
+
+- DigitalExperienceConfig
+  - `digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml`
+- DigitalExperienceBundle
+  - `digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml`
+- Network
+  - `networks/{siteName}.network-meta.xml`
+- CustomSite
+  - `sites/{siteName}.site-meta.xml`
+
+### DigitalExperience Contents
+
+- `digitalExperiences/site/{siteName}1/sfdc_cms__*/{contentApiName}/*`
+- These are the content components defining routes, views, theme layouts, etc. Each component must have a `_meta.json` and `content.json` file.
+
+#### Content Type Descriptions
+
+| Content Type | Description | When to Use |
+|-|-|-|
+| `sfdc_cms__site` | Root site configuration containing site-wide settings | Required for every site; one per site |
+| `sfdc_cms__appPage` | Application page container that groups routes and views | Required; defines the app shell |
+| `sfdc_cms__route` | URL routing definition mapping paths to views | Create one for each page/URL path |
+| `sfdc_cms__view` | Page layout and component structure | Create one for each route; defines page content. Also use to edit existing views (e.g., adding/removing components on a specific page) |
+| `sfdc_cms__brandingSet` | Brand colors, fonts, and styling tokens | Required; defines site-wide styling |
+| `sfdc_cms__languageSettings` | Language and localization configuration | Required; defines supported languages |
+| `sfdc_cms__mobilePublisherConfig` | Mobile app publishing settings | Required for mobile app deployment |
+| `sfdc_cms__theme` | Theme definition referencing layouts and branding | Required; one per site |
+| `sfdc_cms__themeLayout` | Page layout templates used by views | Create layouts for different page structures. Also use to edit existing theme layouts (e.g., updating theme layout, add a component that's persistent across pages) |
+
+**Important:** Creating any new pages require BOTH `sfdc_cms__route` AND `sfdc_cms__view`.
+
+## References
+
+Reference docs within the skill directory. Note that these are **local** and not MCP.
+
+- [bootstrap-template-byo-lwr.md](docs/bootstrap-template-byo-lwr.md) - Site creation, template defaults
+- [configure-content-route.md](docs/configure-content-route.md) - Route creation (custom/object pages)
+- [configure-content-view.md](docs/configure-content-view.md) - View creation/editing (custom/object pages)
+- [configure-content-themeLayout.md](docs/configure-content-themeLayout.md) - Theme layout creation + theme sync
+- [configure-content-brandingSet.md](docs/configure-content-brandingSet.md) - Branding with color patterns/WCAG
+- [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md) - **UUID generation (CRITICAL)** for component and region ids used in views and themeLayout.
+- [handle-ui-components.md](docs/handle-ui-components.md) - Component discovery, schemas, insertion, configuration
+
+## Common Workflows
+
+- See [References](#references) for detailed capabilities.
+- **Always** follow the steps defined in the workflows sequentially whether the task is small, big, quick, or complex.
+
+### Creating a New Site
+
+**Rules**:
+
+- **NEVER** generate the files manually.
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] **ALWAYS** read [bootstrap-template-byo-lwr.md](docs/bootstrap-template-byo-lwr.md) within the skill directory. Do not proceed to the next step without loading the file.
+- [ ] Follow the bootstrap doc strictly on site creation
+
+### Creating and Editing Standard or Object Pages
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] Load [configure-content-route.md](docs/configure-content-route.md)
+- [ ] Load [configure-content-view.md](docs/configure-content-view.md)
+- [ ] Load [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
+- [ ] Follow the instructions of the above docs strictly to accomplish user's goal
+
+### Adding UI Components to Pages
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] Read and follow [handle-ui-components.md](docs/handle-ui-components.md) to add LWCs to LWR sites.
+- [ ] Load and follow [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md) to handle id generation
+- [ ] Read and follow [configure-content-themeLayout.md](docs/configure-content-themeLayout.md) if a component has one of the following requirements:
+  - needs to be "sticky" and persistent across pages
+  - is used as a theme layout
+
+### Creating Theme Layouts
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] Read and follow strictly [configure-content-themeLayout.md](docs/configure-content-themeLayout.md).
+
+### Configuring Branding
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] Read and follow strictly [configure-content-brandingSet.md](docs/configure-content-brandingSet.md) to configure background colors, foreground colors, button colors, and other branding colors that affect all pages.
+
+### CUD Operations on DigitalExperience Contents
+
+- Users can perform create, update, delete operations on DigitalExperience Contents.
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] Determine what content types the user wants to modify
+- [ ] Read and follow strictly the reference doc related to the target content types if the doc exists. e.g., if modifying `sfdc_cms__route`, load [configure-content-route.md](docs/configure-content-route.md).
+- [ ] **Always** Read [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md) if creating or modifying view or theme layout
+- [ ] **Always** Call `execute_metadata_action` to get the schema and examples for that content type **after** loading the corresponding reference docs.
+  - **Call once per content type per user request**: If you're creating/modifying multiple items of the same content type (e.g., creating 3 routes), you only need to call `execute_metadata_action` ONCE for that content type. Reuse the schema and examples for all items of that type within the same user request.
+  - For each unique content type you need to work with, **always** call `execute_metadata_action` using the following:
+
+```json
+{
+  "metadataType": "ExperienceSiteLwr",
+  "actionName": "getSiteContentMetadata",
+  "parameters": {
+    "contentType": "<content type from table above>",
+    "shouldIncludeExamples": true
+  }
+}
+```
+
+### Retrieving Site URLs After Deployment
+
+After successfully deploying the site using `sf project deploy`, use the `execute_metadata_action` MCP tool to get the preview and builder URLs:
+
+```json
+{
+  "metadataType": "ExperienceSiteLwr",
+  "actionName": "getSiteUrls",
+  "parameters": {
+    "siteDevName": "<site developer name>"
+  }
+}
+```
+
+The site developer name can be found in the CustomSite filename (e.g., `sites/MySite.site-meta.xml` → developer name is `MySite`).
+
+If the site is not found, an error message will be returned indicating that the site may not be deployed. Ensure the site has been successfully deployed before calling this action.
+
+### Validation & Deployment
+
+Use `sf` CLI to validate and deploy. Access help docs by attaching `--help`, e.g.:
+
+- `sf project deploy --help`
+- `sf project deploy validate --help`
+
+Note that metadata types are space-delimited.
+
+**Validate**:
+`sf project deploy validate --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}`
+
+**Deploy**:
+`sf project deploy start --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}`