@salesforce/afv-skills 1.2.0 → 1.3.0

package/skills/fetching-webapp-rest-api/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: fetching-webapp-rest-api
+description: REST API usage via the Data SDK fetch method. Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls — only when GraphQL is not sufficient.
+paths:
+  - "**/*.ts"
+  - "**/*.tsx"
+  - "**/*.graphql"
+---
+
+# Salesforce REST API via Data SDK Fetch
+
+Use `sdk.fetch` from the Data SDK when GraphQL is not sufficient. The SDK applies authentication, CSRF handling, and base URL resolution. **Always use optional chaining** (`sdk.fetch?.()`) and handle the case where `fetch` is not available.
+
+Invoke this skill when you need to call Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM endpoints.
+
+## API Version
+
+Use the project's API version. It is typically injected as `__SF_API_VERSION__`; fallback to `"65.0"`:
+
+```typescript
+declare const __SF_API_VERSION__: string;
+const API_VERSION = typeof __SF_API_VERSION__ !== "undefined" ? __SF_API_VERSION__ : "65.0";
+```
+
+## Base Path
+
+URLs are relative to the Salesforce API base. The SDK prepends the correct base path. Use paths starting with `/services/...`.
+
+---
+
+## Chatter API
+
+User and collaboration data. No GraphQL equivalent.
+
+| Endpoint | Method | Purpose |
+| -------- | ------ | ------- |
+| `/services/data/v{version}/chatter/users/me` | GET | Current user (id, name, email, username) |
+
+```typescript
+const sdk = await createDataSDK();
+const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/chatter/users/me`);
+
+if (!response?.ok) throw new Error(`HTTP ${response?.status}`);
+const data = await response.json();
+return { id: data.id, name: data.name };
+```
+
+---
+
+## Connect REST API
+
+File and content operations.
+
+| Endpoint | Method | Purpose |
+| -------- | ------ | ------- |
+| `/services/data/v{version}/connect/file/upload/config` | GET | Upload config (token, uploadUrl) for file uploads |
+
+```typescript
+const sdk = await createDataSDK();
+const configRes = await sdk.fetch?.(`/services/data/v${API_VERSION}/connect/file/upload/config`, {
+  method: "GET",
+});
+
+if (!configRes?.ok) throw new Error(`Failed to get upload config: ${configRes?.status}`);
+const config = await configRes.json();
+const { token, uploadUrl } = config;
+```
+
+---
+
+## Apex REST
+
+Custom Apex REST resources. Requires corresponding Apex classes in the org. CSRF protection is applied automatically for `services/apexrest` URLs.
+
+| Endpoint | Method | Purpose |
+| -------- | ------ | ------- |
+| `/services/apexrest/auth/login` | POST | User login |
+| `/services/apexrest/auth/register` | POST | User registration |
+| `/services/apexrest/auth/forgot-password` | POST | Request password reset |
+| `/services/apexrest/auth/reset-password` | POST | Reset password with token |
+| `/services/apexrest/auth/change-password` | POST | Change password (authenticated) |
+| `/services/apexrest/{resource}` | GET/POST | Custom Apex REST resources |
+
+**Example (login):**
+
+```typescript
+const sdk = await createDataSDK();
+const response = await sdk.fetch?.("/services/apexrest/auth/login", {
+  method: "POST",
+  body: JSON.stringify({ email, password, startUrl: "/" }),
+  headers: { "Content-Type": "application/json", Accept: "application/json" },
+});
+```
+
+Apex REST paths do not include the API version.
+
+---
+
+## UI API (REST)
+
+When GraphQL cannot cover the use case. **Prefer GraphQL** when possible.
+
+| Endpoint | Method | Purpose |
+| -------- | ------ | ------- |
+| `/services/data/v{version}/ui-api/records/{recordId}` | GET | Fetch a single record |
+
+```typescript
+const sdk = await createDataSDK();
+const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/ui-api/records/${recordId}`);
+```
+
+---
+
+## Einstein LLM Gateway
+
+AI features. Requires Einstein API setup.
+
+| Endpoint | Method | Purpose |
+| -------- | ------ | ------- |
+| `/services/data/v{version}/einstein/llm/prompt/generations` | POST | Generate text from Einstein LLM |
+
+```typescript
+const sdk = await createDataSDK();
+const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/einstein/llm/prompt/generations`, {
+  method: "POST",
+  headers: { "Content-Type": "application/json" },
+  body: JSON.stringify({
+    additionalConfig: { applicationName: "PromptTemplateGenerationsInvocable" },
+    promptTextorId: prompt,
+  }),
+});
+
+if (!response?.ok) throw new Error(`Einstein LLM failed (${response?.status})`);
+const data = await response.json();
+return data?.generations?.[0]?.text ?? "";
+```
+
+---
+
+## General Pattern
+
+```typescript
+import { createDataSDK } from "@salesforce/sdk-data";
+
+const sdk = await createDataSDK();
+
+if (!sdk.fetch) {
+  throw new Error("Data SDK fetch is not available in this context");
+}
+
+const response = await sdk.fetch(url, {
+  method: "GET", // or POST, PUT, PATCH, DELETE
+  headers: { "Content-Type": "application/json", Accept: "application/json" },
+  body: method !== "GET" ? JSON.stringify(payload) : undefined,
+});
+
+if (!response.ok) throw new Error(`HTTP ${response.status}`);
+const data = await response.json();
+```
+
+---
+
+## Reference
+
+- Parent: `accessing-data` — enforces Data SDK usage for all Salesforce data fetches
+- GraphQL: `using-graphql` — use for record queries and mutations when possible
+- `createRecord` from `@salesforce/webapp-experimental/api` for UI API record creation (uses SDK internally)

package/skills/{salesforce-custom-application → generating-custom-application}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-custom-application
+name: generating-custom-application
 description: Use this skill when users need to create or configure Salesforce Custom Applications. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Always use this skill for custom application work.
 ---
 
@@ -11,7 +11,6 @@ Use this skill when you need to:
 - Configure application navigation and branding
 - Set up custom page layouts for objects
 - Troubleshoot deployment errors related to custom applications
-
 # CustomApplication (Lightning App) Metadata Specification
 
 ## Overview

package/skills/{salesforce-custom-field → generating-custom-field}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-custom-field
+name: generating-custom-field
 description: Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, or field metadata. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, or formula issues. Always use this skill for any custom field metadata work, field generation, or field troubleshooting.
 ---
 

package/skills/{salesforce-custom-lightning-type → generating-custom-lightning-type}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-custom-lightning-type
+name: generating-custom-lightning-type
 description: Use this skill when users need to create Custom Lightning Types (CLTs) for Einstein Agent actions or structured input/output schemas. Trigger when users mention CLT, Custom Lightning Types, JSON schemas for agents, type definitions, lightning__objectType, or editor/renderer configurations. This is complex - always use this skill for CLT work.
 ---
 
@@ -103,9 +103,11 @@ When strict validation is enabled (`unevaluatedProperties: false`), keep each pr
      - Top-level `editor` object.
      - Use `editor.componentOverrides` for component overrides.
      - Use `editor.layout` for layout.
+     - **DEPRECATED**: Do NOT use `propertyRenderers` or `view` — these are legacy keys. Always use `componentOverrides` and `layout` instead.
    - **Root override pattern** (most common for fully custom editing UI):
      - `editor.componentOverrides["$"] = { "definition": "c/<yourEditorComponent>", "attributes": { ... } }`
      - When passing schema data into a custom LWC, use attribute mapping with the `{!$attrs.<name>}` syntax: e.g. `"attributes": { "myField": "{!$attrs.value}" }` so the runtime binds schema values to your component's attributes.
+     - **CRITICAL**: The `<name>` in `{!$attrs.<name>}` must be a property defined in your type schema. For example, if your schema has a property called `temperature`, use `{!$attrs.temperature}`, not `{!$attrs.value}` unless `value` is an actual property.
    - **Property-level override pattern** (for individual fields):
      - `editor.componentOverrides["<propertyName>"] = { "definition": "es_property_editors/<...>" }`
      - **Valid editor components** (examples): `es_property_editors/inputText`, `es_property_editors/inputNumber`, `es_property_editors/inputRichText`, `es_property_editors/inputImage`, `es_property_editors/inputTextarea`. **Do not use** `es_property_editors/inputList`.
@@ -113,6 +115,7 @@ When strict validation is enabled (`unevaluatedProperties: false`), keep each pr
    - **Layout pattern**:
      - `editor.layout.definition = "lightning/verticalLayout"`
      - `editor.layout.children[*].definition = "lightning/propertyLayout"` with `attributes.property = "<propertyName>"`
+     - **CRITICAL**: `lightning/propertyLayout` only accepts the `property` attribute. Do NOT add `label`, `title`, or any other attributes — these will fail validation with `additionalProperties: false` errors.
    - **Avoid known-invalid patterns**:
      - Do not use `es_property_editors/inputList`.
      - Do not use `itemSchema` attributes.
@@ -121,18 +124,41 @@ When strict validation is enabled (`unevaluatedProperties: false`), keep each pr
      - Top-level `renderer` object.
      - Use `renderer.componentOverrides` for component overrides.
      - Use `renderer.layout` for layout.
+     - **DEPRECATED**: Do NOT use `propertyRenderers` or `view` — these are legacy keys. Always use `componentOverrides` and `layout` instead.
    - **Root override pattern** (most common for fully custom rendering UI):
      - `renderer.componentOverrides["$"] = { "definition": "c/<yourRendererComponent>", "attributes": { ... } }`
      - Use `{!$attrs.<name>}` in attribute mappings when binding schema data to custom renderer component attributes.
+     - **CRITICAL**: Attribute mappings like `{!$attrs.propertyName}` must reference properties that **actually exist** in your type schema. Referencing non-existent properties will fail validation.
+     - **Type matching**: Attribute values must match the expected type for the component. For example, if a component expects a string attribute, passing an integer will fail validation.
    - **Property-level override pattern**:
      - `renderer.componentOverrides["<propertyName>"] = { "definition": "es_property_editors/outputText" | "es_property_editors/outputNumber" | "es_property_editors/outputImage" | ... }`. **Valid renderer components** (examples): `es_property_editors/outputText`, `es_property_editors/outputNumber`, `es_property_editors/outputImage`. Avoid input-style components in the renderer.
+   - **Layout pattern for renderer**:
+     - `renderer.layout.definition = "lightning/verticalLayout"`
+     - `renderer.layout.children[*].definition = "lightning/propertyLayout"` with `attributes.property = "<propertyName>"`
+     - **CRITICAL**: Same as editor layouts, `lightning/propertyLayout` only accepts the `property` attribute. Do NOT add `label`, `title`, or any other attributes.
    - **Collection renderer** (for root-level `lightning__listType` properties): Use `collection.renderer.componentOverrides["$"] = { "definition": "c/<yourListRendererComponent>" }` or `es_property_editors/genericListTypeRenderer` to render the list.
 5. **Place files in the correct bundle structure**
    - `lightningTypes/<TypeName>/schema.json`
    - (Optional) `lightningTypes/<TypeName>/lightningDesktopGenAi/editor.json`
    - (Optional) `lightningTypes/<TypeName>/lightningDesktopGenAi/renderer.json`
    - For Gen AI / Copilot the standard path is `lightningDesktopGenAi/`. Other targets (e.g. Experience Builder, Mobile Copilot, Enhanced Web Chat) use different subfolders when supported: `experienceBuilder/`, `lightningMobileGenAi/`, `enhancedWebChat/`.
-6. **Deploy and validate**
+6. **Configure custom LWC components (if using custom components)**
+   - **CRITICAL**: Custom LWC components referenced in editor/renderer configs MUST have the correct target configuration in their `-meta.xml` files:
+     - **For editor components** (`c/<componentName>` used in `editor.json`): The LWC's `-meta.xml` file must include `<target>lightning__AgentforceInput</target>`
+     - **For renderer components** (`c/<componentName>` used in `renderer.json`): The LWC's `-meta.xml` file must include `<target>lightning__AgentforceOutput</target>`
+   - Without the correct target, deployment will fail with: `Invalid target configuration. To use 'c/componentName' as a renderer/editor, your js-meta.xml file must include valid target 'lightning__AgentforceOutput/Input'.`
+   - Example `-meta.xml` for a renderer component:
+     ```xml
+     <?xml version="1.0" encoding="UTF-8"?>
+     <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
+         <apiVersion>60.0</apiVersion>
+         <isExposed>true</isExposed>
+         <targets>
+             <target>lightning__AgentforceOutput</target>
+         </targets>
+     </LightningComponentBundle>
+     ```
+7. **Deploy and validate**
    - Deploy the bundle using your org's standard metadata deployment flow (e.g. Salesforce CLI or IDE). The MCP client or tooling in use should provide or integrate with the appropriate deploy/retrieve commands for Lightning Type bundles.
    - Validate incrementally: if deployment fails, remove disallowed keywords first (especially `examples`, `items`, nested `lightning:type`).
 
@@ -144,6 +170,11 @@ When strict validation is enabled (`unevaluatedProperties: false`), keep each pr
 | Array property rejected | Use of `items` (or `lightning:type` in nested arrays) rejected by validator | For nested arrays: keep only `type: "array"`. For root arrays: use minimal structure; remove `items` if rejected |
 | Apex-based CLT rejected | Extra fields added (e.g., `type`, `properties`) | Use only `title`, optional `description`, and `lightning:type` |
 | Editor config rejected | Use of invalid patterns (`es_property_editors/inputList`, `itemSchema`) or unrecognized top-level keys | Use `editor.componentOverrides` and `editor.layout`; keep config minimal |
+| `additionalProperties` error on layout attributes | Adding `label` or other attributes to `lightning/propertyLayout` | Only use `property` attribute in `lightning/propertyLayout`. Remove `label`, `title`, or any other attributes |
+| Invalid target configuration for custom LWC | Custom LWC component's `-meta.xml` missing required target (`lightning__AgentforceInput` or `lightning__AgentforceOutput`) | Add correct target to LWC's `-meta.xml`: use `lightning__AgentforceInput` for editors, `lightning__AgentforceOutput` for renderers |
+| Attribute mapping doesn't exist in type schema | Using `{!$attrs.propertyName}` where `propertyName` is not defined in schema | Ensure all attribute mappings reference actual properties in your type schema's `properties` section |
+| `additionalProperties` error with deprecated keys | Using `propertyRenderers` or `view` in editor/renderer config | Replace deprecated `propertyRenderers` with `componentOverrides` and `view` with `layout` |
+| Type mismatch in component attributes | Passing wrong type for component attribute (e.g., integer instead of string) | Ensure attribute values match the expected type defined by the component |
 
 ## Verification Checklist
 - [ ] Root schema has `type: "object"`, `title`, `lightning:type: "lightning__objectType"`, and `unevaluatedProperties: false`
@@ -155,3 +186,6 @@ When strict validation is enabled (`unevaluatedProperties: false`), keep each pr
 - [ ] Bundle structure and filenames match Lightning Types requirements
 - [ ] Editor config uses only allowed patterns (no `es_property_editors/inputList`, no `itemSchema`); use valid components (e.g. `es_property_editors/inputText`, `es_property_editors/inputNumber`) or custom `c/` components
 - [ ] Renderer config uses output-style components (e.g. `es_property_editors/outputText`, `es_property_editors/outputNumber`) where applicable, not input editors
+- [ ] Layout configurations use `lightning/propertyLayout` with ONLY the `property` attribute (no `label`, `title`, or other attributes)
+- [ ] All attribute mappings (`{!$attrs.propertyName}`) reference properties that exist in the type schema
+- [ ] Custom LWC components have correct targets in `-meta.xml`: `lightning__AgentforceInput` for editors, `lightning__AgentforceOutput` for renderers

package/skills/{salesforce-custom-object → generating-custom-object}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-custom-object
+name: generating-custom-object
 description: Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like "create a custom object", "generate object metadata", "set up an object for...", or when they're troubleshooting object deployment errors especially around sharing models and Master-Detail relationships. Always use this skill for any custom object metadata work.
 ---
 

package/skills/{salesforce-custom-tab → generating-custom-tab}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-custom-tab
+name: generating-custom-tab
 description: Use this skill when users need to create or configure Salesforce Custom Tabs. Trigger when users mention tabs, navigation tabs, object tabs, web tabs, Visualforce tabs, Lightning component tabs, app page tabs, or tab configuration. Also use when users want to add navigation to custom objects, create tabs for external content, or set up Lightning page tabs. Always use this skill for any custom tab work.
 ---
 

package/skills/{salesforce-experience-lwr-site → generating-experience-lwr-site}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-experience-lwr-site
+name: generating-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.
 ---
 

package/skills/{salesforce-experience-lwr-site → generating-experience-lwr-site}/docs/handle-ui-components.md

@@ -212,4 +212,4 @@ In this example the component threeColumn has 3 slots, named left, center, and r
     "definition" : "c:threeColumn",
     "id" : "b9e517c5-90ac-49e9-91b7-3730512c95a3",
     "type" : "component"
-}
+}

package/skills/generating-experience-react-site/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: generating-experience-react-site
+description: Use this skill when users need to create or configure a Salesforce Digital Experience Site specifically for hosting a React web application. Trigger when users mention creating an Experience site for a React app, setting up a React site on Salesforce, configuring Network/CustomSite/DigitalExperience metadata for a web app, or deploying site infrastructure for a React application. Also trigger when users mention site URL path prefixes, app namespaces, appDevName, guest access configuration, DigitalExperienceConfig, DigitalExperienceBundle, or sfdc_cms__site content types in the context of React apps. Always use this skill for any React web application site creation or site infrastructure configuration work, even if the user just says "create a site for my React app" or "set up the site for my web application."
+---
+
+# Digital Experience Site for React Web Applications
+Create and configure Digital Experience Sites that host React web applications on Salesforce. This skill generates the minimum necessary site infrastructure — Network, CustomSite, DigitalExperienceConfig, DigitalExperienceBundle, and the `sfdc_cms__site` content type — so a React app can be served from Salesforce.
+
+React sites differ from standard LWR sites: they don't need routes, views, theme layouts, or branding sets. The site acts as a thin container (`appContainer: true`) that delegates rendering to the React application referenced by `appSpace`.
+
+## Required Properties
+Resolve all five properties before generating any metadata. Each has a fallback chain — work through each option in order until a value is found.
+
+| Property | Format | How to Resolve |
+|----------|--------|----------------|
+| **siteName** | `UpperCamelCase` (e.g., `MyCommunity`) | Ask user or derive from context |
+| **siteUrlPathPrefix** | `kebab-case` (e.g., `my-community`) | User-provided, or convert siteName to kebab-case |
+| **appNamespace** | String | `namespace` in `sfdx-project.json` → `sf data query -q "SELECT NamespacePrefix FROM Organization" --target-org ${usernameOrAlias}` → default `c` |
+| **appDevName** | String | `webApplication` metadata in the project → `sf data query -q "SELECT DeveloperName FROM WebApplication" --target-org ${usernameOrAlias}` → default to siteName |
+| **enableGuestAccess** | Boolean | Ask user whether unauthenticated guest users can access site APIs → default `false` |
+
+The `appNamespace` and `appDevName` properties connect the site to the correct React application. Getting these wrong means the site deploys but shows a blank page, so take care to resolve them from real project data.
+
+## Generation Workflow
+### Step 1: Resolve All Required Properties
+Determine values for all five properties before constructing anything. Use the resolution strategies in the table above, falling through each option until a value is found.
+
+### Step 2: Create the Project Structure
+Call the `get_metadata_api_context` MCP tool to retrieve schemas for `Network`, `CustomSite`, `DigitalExperienceConfig`, and `DigitalExperienceBundle` metadata types. These schemas define the valid XML structure for each file.
+
+Create any files and directories that don't already exist, using these paths:
+
+| Metadata Type | Path |
+|--------------|------|
+| Network | `networks/{siteName}.network-meta.xml` |
+| CustomSite | `sites/{siteName}.site-meta.xml` |
+| DigitalExperienceConfig | `digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml` |
+| DigitalExperienceBundle | `digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml` |
+| DigitalExperience (sfdc_cms__site) | `digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/*` |
+
+The DigitalExperience directory contains only `_meta.json` and `content.json`. Do not create any directories other than `sfdc_cms__site` inside the bundle.
+
+### Step 3: Populate All Metadata Fields
+Use the default templates in the docs below. Values in `{braces}` are resolved property references — substitute them with the actual values from Step 1.
+
+| Metadata Type | Template Reference |
+|--------------|-------------------|
+| Network | [configure-metadata-network.md](docs/configure-metadata-network.md) |
+| CustomSite | [configure-metadata-custom-site.md](docs/configure-metadata-custom-site.md) |
+| DigitalExperienceConfig | [configure-metadata-digital-experience-config.md](docs/configure-metadata-digital-experience-config.md) |
+| DigitalExperienceBundle | [configure-metadata-digital-experience-bundle.md](docs/configure-metadata-digital-experience-bundle.md) |
+| DigitalExperience (sfdc_cms__site) | [configure-metadata-digital-experience.md](docs/configure-metadata-digital-experience.md) |
+
+### Step 4: Resolve Additional Configurations
+Address any extra configurations the user requests. Use the schemas returned by `get_metadata_api_context` in Step 2 to understand each field's purpose, and update only the minimum necessary fields.
+
+## Verification Checklist
+Before deploying, confirm:
+
+- [ ] All five required properties are resolved
+- [ ] All metadata directories and files exist per the project structure
+- [ ] All metadata fields are populated per the templates and user requests
+- [ ] `appSpace` in `content.json` matches an existing `WebApplication` metadata record
+- [ ] Deployment validates successfully:
+```bash
+sf project deploy validate --metadata Network CustomSite DigitalExperienceConfig DigitalExperienceBundle DigitalExperience --target-org ${usernameOrAlias}
+```

package/skills/generating-experience-react-site/docs/configure-metadata-custom-site.md

@@ -0,0 +1,41 @@
+# Configure Metadata: CustomSite
+
+## Purpose
+This configuration file creates a **net-new, default** CustomSite metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing CustomSite record. Use this template only when provisioning a brand-new React site.
+
+## File Location
+```
+sites/{siteName}.site-meta.xml
+```
+
+## Default Template
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomSite xmlns="http://soap.sforce.com/2006/04/metadata">
+    <active>true</active>
+    <allowGuestPaymentsApi>false</allowGuestPaymentsApi>
+    <allowHomePage>false</allowHomePage>
+    <allowStandardAnswersPages>false</allowStandardAnswersPages>
+    <allowStandardIdeasPages>false</allowStandardIdeasPages>
+    <allowStandardLookups>false</allowStandardLookups>
+    <allowStandardPortalPages>true</allowStandardPortalPages>
+    <allowStandardSearch>false</allowStandardSearch>
+    <authorizationRequiredPage>CommunitiesLogin</authorizationRequiredPage>
+    <bandwidthExceededPage>BandwidthExceeded</bandwidthExceededPage>
+    <browserXssProtection>true</browserXssProtection>
+    <cachePublicVisualforcePagesInProxyServers>true</cachePublicVisualforcePagesInProxyServers>
+    <clickjackProtectionLevel>SameOriginOnly</clickjackProtectionLevel>
+    <contentSniffingProtection>true</contentSniffingProtection>
+    <enableAuraRequests>true</enableAuraRequests>
+    <fileNotFoundPage>FileNotFound</fileNotFoundPage>
+    <genericErrorPage>Exception</genericErrorPage>
+    <inMaintenancePage>InMaintenance</inMaintenancePage>
+    <indexPage>CommunitiesLanding</indexPage>
+    <masterLabel>{siteName}</masterLabel>
+    <redirectToCustomDomain>false</redirectToCustomDomain>
+    <referrerPolicyOriginWhenCrossOrigin>true</referrerPolicyOriginWhenCrossOrigin>
+    <selfRegPage>CommunitiesSelfReg</selfRegPage>
+    <siteType>ChatterNetwork</siteType>
+    <urlPathPrefix>{siteUrlPathPrefix}vforcesite</urlPathPrefix>
+</CustomSite>
+```

package/skills/generating-experience-react-site/docs/configure-metadata-digital-experience-bundle.md

@@ -0,0 +1,17 @@
+# Configure Metadata: DigitalExperienceBundle
+
+## Purpose
+This configuration file creates a **net-new, default** DigitalExperienceBundle metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing DigitalExperienceBundle record. Use this template only when provisioning a brand-new React site.
+
+## File Location
+```
+digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml
+```
+
+## Default Template
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<DigitalExperienceBundle xmlns="http://soap.sforce.com/2006/04/metadata">
+    <label>{siteName}1</label>
+</DigitalExperienceBundle>
+```

package/skills/generating-experience-react-site/docs/configure-metadata-digital-experience-config.md

@@ -0,0 +1,21 @@
+# Configure Metadata: DigitalExperienceConfig
+
+## Purpose
+This configuration file creates a **net-new, default** DigitalExperienceConfig metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing DigitalExperienceConfig record. Use this template only when provisioning a brand-new React site.
+
+## File Location
+```
+digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml
+```
+
+## Default Template
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<DigitalExperienceConfig xmlns="http://soap.sforce.com/2006/04/metadata">
+    <label>{siteName}</label>
+    <site>
+        <urlPathPrefix>{siteUrlPathPrefix}</urlPathPrefix>
+    </site>
+    <space>site/{siteName}1</space>
+</DigitalExperienceConfig>
+```

package/skills/generating-experience-react-site/docs/configure-metadata-digital-experience.md

@@ -0,0 +1,38 @@
+# Configure Metadata: DigitalExperience (sfdc_cms__site)
+
+## Purpose
+These configuration files create **net-new, default** DigitalExperience content records (`sfdc_cms__site` type) for a Digital Experience React Site. They are not intended to edit or modify existing DigitalExperience content. Use these templates only when provisioning a brand-new React site.
+
+The `appContainer: true` and `appSpace` fields in `content.json` are what make this a React site rather than a standard LWR site. The `appSpace` value follows the format `{namespace}__{developerName}` and must match a deployed `WebApplication` metadata record.
+
+## File Location
+The DigitalExperience directory contains only `_meta.json` and `content.json`. Do not create any directories other than `sfdc_cms__site` inside the bundle.
+
+```
+digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/_meta.json
+digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/content.json
+```
+
+## Default Templates
+### `_meta.json`
+```json
+{
+  "apiName": "{siteName}1",
+  "path": "",
+  "type": "sfdc_cms__site"
+}
+```
+
+### `content.json`
+```json
+{
+  "type": "sfdc_cms__site",
+  "title": "{siteName}",
+  "urlName": "{siteUrlPathPrefix}",
+  "contentBody": {
+    "authenticationType": "AUTHENTICATED_WITH_PUBLIC_ACCESS_ENABLED",
+    "appContainer": true,
+    "appSpace": "{appNamespace}__{appDevName}"
+  }
+}
+```

package/skills/generating-experience-react-site/docs/configure-metadata-network.md

@@ -0,0 +1,72 @@
+# Configure Metadata: Network
+
+## Purpose
+This configuration file creates a **net-new, default** Network metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing Network record. Use this template only when provisioning a brand-new React site.
+
+## File Location
+```
+networks/{siteName}.network-meta.xml
+```
+
+## Default Template
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<Network xmlns="http://soap.sforce.com/2006/04/metadata">
+    <allowInternalUserLogin>false</allowInternalUserLogin>
+    <allowMembersToFlag>false</allowMembersToFlag>
+    <changePasswordTemplate>unfiled$public/CommunityChangePasswordEmailTemplate</changePasswordTemplate>
+    <disableReputationRecordConversations>true</disableReputationRecordConversations>
+    <emailSenderAddress>admin@company.com</emailSenderAddress>
+    <emailSenderName>{siteName}</emailSenderName>
+    <embeddedLoginEnabled>false</embeddedLoginEnabled>
+    <enableApexCDNCaching>true</enableApexCDNCaching>
+    <enableCustomVFErrorPageOverrides>false</enableCustomVFErrorPageOverrides>
+    <enableDirectMessages>true</enableDirectMessages>
+    <enableExpFriendlyUrlsAsDefault>false</enableExpFriendlyUrlsAsDefault>
+    <enableExperienceBundleBasedSnaOverrideEnabled>true</enableExperienceBundleBasedSnaOverrideEnabled>
+    <enableGuestChatter>{enableGuestAccess}</enableGuestChatter>
+    <enableGuestFileAccess>false</enableGuestFileAccess>
+    <enableGuestMemberVisibility>false</enableGuestMemberVisibility>
+    <enableImageOptimizationCDN>true</enableImageOptimizationCDN>
+    <enableInvitation>false</enableInvitation>
+    <enableKnowledgeable>false</enableKnowledgeable>
+    <enableLWRExperienceConnectedApp>false</enableLWRExperienceConnectedApp>
+    <enableMemberVisibility>false</enableMemberVisibility>
+    <enableNicknameDisplay>true</enableNicknameDisplay>
+    <enablePrivateMessages>false</enablePrivateMessages>
+    <enableReputation>false</enableReputation>
+    <enableShowAllNetworkSettings>false</enableShowAllNetworkSettings>
+    <enableSiteAsContainer>true</enableSiteAsContainer>
+    <enableTalkingAboutStats>true</enableTalkingAboutStats>
+    <enableTopicAssignmentRules>true</enableTopicAssignmentRules>
+    <enableTopicSuggestions>false</enableTopicSuggestions>
+    <enableUpDownVote>false</enableUpDownVote>
+    <forgotPasswordTemplate>unfiled$public/CommunityForgotPasswordEmailTemplate</forgotPasswordTemplate>
+    <gatherCustomerSentimentData>false</gatherCustomerSentimentData>
+    <headlessForgotPasswordTemplate>unfiled$public/CommunityHeadlessForgotPasswordTemplate</headlessForgotPasswordTemplate>
+    <headlessRegistrationTemplate>unfiled$public/CommunityHeadlessRegistrationTemplate</headlessRegistrationTemplate>
+    <networkMemberGroups>
+        <profile>admin</profile>
+    </networkMemberGroups>
+    <networkPageOverrides>
+        <changePasswordPageOverrideSetting>Standard</changePasswordPageOverrideSetting>
+        <forgotPasswordPageOverrideSetting>Designer</forgotPasswordPageOverrideSetting>
+        <homePageOverrideSetting>Designer</homePageOverrideSetting>
+        <loginPageOverrideSetting>Designer</loginPageOverrideSetting>
+        <selfRegProfilePageOverrideSetting>Designer</selfRegProfilePageOverrideSetting>
+    </networkPageOverrides>
+    <newSenderAddress>admin@company.com</newSenderAddress>
+    <picassoSite>{siteName}1</picassoSite>
+    <selfRegistration>false</selfRegistration>
+    <sendWelcomeEmail>true</sendWelcomeEmail>
+    <site>{siteName}</site>
+    <siteArchiveStatus>NotArchived</siteArchiveStatus>
+    <status>Live</status>
+    <tabs>
+        <defaultTab>home</defaultTab>
+        <standardTab>Chatter</standardTab>
+    </tabs>
+    <urlPathPrefix>{siteUrlPathPrefix}vforcesite</urlPathPrefix>
+    <welcomeTemplate>unfiled$public/CommunityWelcomeEmailTemplate</welcomeTemplate>
+</Network>
+```