@salesforce/afv-skills 1.22.0 → 1.23.0

package/skills/generating-ui-bundle-features/SKILL.md

@@ -1,47 +0,0 @@
----
-name: generating-ui-bundle-features
-description: "MUST activate when the project contains a uiBundles/*/src/ directory and the user wants to add authentication or search to their app. Use this skill when adding authentication or search to a UI bundle app. Only covers two features: authentication (login, logout, protected routes, session management) and search (global search across pages and content). Always use this skill for these two features instead of building from scratch."
-metadata:
-  version: "1.0"
----
-
-# UI Bundle Features
-
-## Installing Pre-built Features
-
-Always check for an existing feature before building something from scratch. The features CLI installs pre-built, tested packages into Salesforce UI bundles — from foundational UI libraries (shadcn/ui) to full-stack capabilities (authentication, search, navigation, GraphQL, Agentforce AI).
-
-### Workflow
-
-1. **Search project code first** — check `src/` for existing implementations before installing anything. Scope searches to `src/` to avoid matching `node_modules/` or `dist/`.
-
-2. **Search available features** — use `npx @salesforce/ui-bundle-features list` with `--search <query>` to filter by keyword. Use `--verbose` for full descriptions.
-
-3. **Describe a feature** — use `npx @salesforce/ui-bundle-features describe <feature>` to see components, dependencies, copy operations, and example files.
-
-4. **Install** — use `npx @salesforce/ui-bundle-features install <feature> --ui-bundle-dir <name>`. Key options:
-   - `--dry-run` to preview changes
-   - `--yes` for non-interactive mode (skips conflicts)
-   - `--on-conflict error` to detect conflicts, then `--conflict-resolution <file>` to resolve them
-
-If no matching feature is found, ask the user before building a custom implementation — a relevant feature may exist under a different name.
-
-### Conflict Handling
-
-In non-interactive environments, use the two-pass approach: first run with `--on-conflict error` to detect conflicts, then create a resolution JSON file (`{ "path": "skip" | "overwrite" }`) and re-run with `--conflict-resolution`.
-
-### Post-install: Integrating Example Files
-
-Features may include `__example__` files showing integration patterns. For each:
-
-1. Read the example file to understand the pattern
-2. Read the target file (shown in `describe` output)
-3. Apply the pattern from the example into the target
-4. Delete the example file after successful integration
-
-### Hint Placeholders
-
-Some copy paths use `<descriptive-name>` placeholders (e.g., `<desired-page-with-search-input>`) that the CLI does not resolve. After installation, rename or relocate these files to the intended target, or integrate their patterns into an existing file.
-
-
-

package/skills/generating-ui-bundle-metadata/SKILL.md

@@ -1,153 +0,0 @@
----
-name: generating-ui-bundle-metadata
-description: "MUST activate when the project contains a uiBundles/*/src/ directory and scaffolding a new UI bundle or app, or when editing ui-bundle.json, .uibundle-meta.xml, or CSP trusted site files. Use this skill when scaffolding with sf template generate ui-bundle, configuring ui-bundle.json (routing, headers, outputDir), or registering CSP Trusted Sites. Activate when the task involves files matching *.uibundle-meta.xml, ui-bundle.json, or cspTrustedSites/*.cspTrustedSite-meta.xml."
-metadata:
-  version: "1.0"
----
-
-# UI Bundle Metadata
-
-## Scaffolding a New UI Bundle
-
-Use `sf template generate ui-bundle` to create new apps — not create-react-app, Vite, or other generic scaffolds.
-
-**Always pass `--template reactbasic`** to scaffold a React-based bundle.
-
-**UI bundle name (`-n`):** Alphanumerical only — no spaces, hyphens, underscores, or special characters.
-
-**Example:**
-```bash
-sf template generate ui-bundle -n CoffeeBoutique --template reactbasic
-```
-
-After generation:
-1. Replace all default boilerplate — "React App", "Vite + React", default `<title>`, placeholder text
-2. Populate the home page with real content (landing section, banners, hero, navigation)
-3. Update navigation and placeholders (see the `building-ui-bundle-frontend` skill)
-4. **Configure a hosting target** — a UI bundle without a `<target>` in its meta XML will not be visible in the org. Use `generating-ui-bundle-custom-app` for internal (App Launcher) apps or `generating-ui-bundle-site` for external (Experience Site) apps.
-
-Always install dependencies before running any scripts in the UI bundle directory.
-
----
-
-## UIBundle Bundle
-
-A UIBundle bundle lives under `uiBundles/<AppName>/` and must contain:
-
-- `<AppName>.uibundle-meta.xml` — filename must exactly match the folder name
-- A build output directory (default: `dist/`) with at least one file
-
-### Meta XML
-
-Required fields: `masterLabel`, `version` (max 20 chars), `isActive` (boolean).
-Optional: `description` (max 255 chars), `target`.
-
-#### Target Field
-
-The `<target>` element specifies where the UI bundle is hosted:
-
-| Value | Use Case | Companion Metadata |
-|-------|----------|-------------------|
-| `Experience` | External-facing site via Digital Experience | Network, CustomSite, DigitalExperienceConfig, DigitalExperienceBundle |
-| `CustomApplication` | Internal app via Lightning App Launcher | CustomApplication (`applications/*.app-meta.xml`) |
-
-A `<target>` is **required** for the app to be accessible in a Salesforce org. A UI bundle deployed without a target will not appear anywhere — no App Launcher entry, no Experience Site URL. Always pair the bundle with one of:
-- `generating-ui-bundle-site` (for `Experience` target)
-- `generating-ui-bundle-custom-app` (for `CustomApplication` target)
-
-**Example with Experience target:**
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<UIBundle xmlns="http://soap.sforce.com/2006/04/metadata">
-    <masterLabel>propertyrentalapp</masterLabel>
-    <description>A Salesforce UI Bundle.</description>
-    <isActive>true</isActive>
-    <version>1</version>
-    <target>Experience</target>
-</UIBundle>
-```
-
-**Example with CustomApplication target:**
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<UIBundle xmlns="http://soap.sforce.com/2006/04/metadata">
-    <masterLabel>propertymanagementapp</masterLabel>
-    <description>A Salesforce UI Bundle.</description>
-    <isActive>true</isActive>
-    <version>1</version>
-    <target>CustomApplication</target>
-</UIBundle>
-```
-
-### ui-bundle.json
-
-Optional file. Allowed top-level keys: `outputDir`, `routing`, `headers`.
-
-**Constraints:**
-- Valid UTF-8 JSON, max 100 KB
-- Root must be a non-empty object (never `{}`, arrays, or primitives)
-
-**Path safety** (applies to `outputDir` and `routing.fallback`): Reject backslashes, leading `/` or `\`, `..` segments, null/control characters, globs (`*`, `?`, `**`), and `%`. All resolved paths must stay within the bundle.
-
-#### outputDir
-Non-empty string referencing a subdirectory (not `.` or `./`). Directory must exist and contain at least one file.
-
-#### routing
-If present, must be a non-empty object. Allowed keys: `rewrites`, `redirects`, `fallback`, `trailingSlash`, `fileBasedRouting`.
-
-- **trailingSlash**: `"always"`, `"never"`, or `"auto"`
-- **fileBasedRouting**: boolean
-- **fallback**: non-empty string satisfying path safety; target file must exist
-- **rewrites**: non-empty array of `{ route?, rewrite }` objects — e.g., `{ "route": "/app/:path*", "rewrite": "/index.html" }`
-- **redirects**: non-empty array of `{ route?, redirect, statusCode? }` objects — statusCode must be 301, 302, 307, or 308
-
-#### headers
-Non-empty array of `{ source, headers: [{ key, value }] }` objects.
-
-**Example:**
-```json
-{
-  "routing": {
-    "rewrites": [{ "route": "/app/:path*", "rewrite": "/index.html" }],
-    "trailingSlash": "never"
-  },
-  "headers": [
-    {
-      "source": "/assets/**",
-      "headers": [{ "key": "Cache-Control", "value": "public, max-age=31536000, immutable" }]
-    }
-  ]
-}
-```
-
-**Never suggest:** `{}` as root, empty `"routing": {}`, empty arrays, `[{}]`, `"outputDir": "."`, `"outputDir": "./"`.
-
----
-
-## CSP Trusted Sites
-
-Salesforce enforces Content Security Policy headers. Any external domain not registered as a CSP Trusted Site will be blocked (images won't load, API calls fail, fonts missing).
-
-### When to Create
-
-Whenever the app references a new external domain: CDN images, external fonts, third-party APIs, map tiles, iframes, external stylesheets.
-
-### Steps
-
-1. **Identify external domains** — extract the origin (scheme + host) from each external URL in the code
-2. **Check existing registrations** — look in `force-app/main/default/cspTrustedSites/`
-3. **Map resource type to CSP directive:**
-
-| Resource Type | Directive Field |
-|--------------|----------------|
-| Images | `isApplicableToImgSrc` |
-| API calls (fetch, XHR) | `isApplicableToConnectSrc` |
-| Fonts | `isApplicableToFontSrc` |
-| Stylesheets | `isApplicableToStyleSrc` |
-| Video / audio | `isApplicableToMediaSrc` |
-| Iframes | `isApplicableToFrameSrc` |
-
-Always also set `isApplicableToConnectSrc` to `true` for preflight/redirect handling.
-
-4. **Create the metadata file** — follow `implementation/csp-metadata-format.md` for the `.cspTrustedSite-meta.xml` format. Place in `force-app/main/default/cspTrustedSites/`.
-

package/skills/generating-ui-bundle-metadata/implementation/csp-metadata-format.md

@@ -1,281 +0,0 @@
-# CSP Trusted Site Metadata — Implementation Guide
-
-## File location
-
-```
-force-app/main/default/cspTrustedSites/{Name}.cspTrustedSite-meta.xml
-```
-
-The `cspTrustedSites/` directory must be a direct child of `force-app/main/default/`. Create it if it does not exist.
-
----
-
-## File naming convention
-
-The file name must match the `<fullName>` value inside the XML, with `.cspTrustedSite-meta.xml` appended.
-
-| Domain | fullName | File name |
-|--------|----------|-----------|
-| `https://images.unsplash.com` | `Unsplash_Images` | `Unsplash_Images.cspTrustedSite-meta.xml` |
-| `https://api.open-meteo.com` | `Open_Meteo_API` | `Open_Meteo_API.cspTrustedSite-meta.xml` |
-| `https://tile.openstreetmap.org` | `OpenStreetMap_Tiles` | `OpenStreetMap_Tiles.cspTrustedSite-meta.xml` |
-
-**Naming rules:**
-- Use PascalCase with underscores separating words (e.g. `Google_Fonts_Static`)
-- Name should describe the provider and resource type (e.g. `Pexels_Videos`, not just `Pexels`)
-- Must be unique across the org
-- Maximum 80 characters
-
----
-
-## XML template
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>{UNIQUE_NAME}</fullName>
-    <description>{DESCRIPTION}</description>
-    <endpointUrl>{HTTPS_ORIGIN}</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>{true|false}</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>{true|false}</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>{true|false}</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>{true|false}</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>{true|false}</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>{true|false}</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
----
-
-## Field reference
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| `fullName` | Yes | Unique API name. Must match the file name (before `.cspTrustedSite-meta.xml`). |
-| `description` | Yes | Human-readable purpose. Start with "Allow access to..." |
-| `endpointUrl` | Yes | The external origin (scheme + host). Must start with `https://`. No trailing slash. No path. |
-| `isActive` | Yes | Always `true` for new entries. Set `false` to disable without deleting. |
-| `context` | Yes | `All` (applies to all contexts). Other values: `LEX` (Lightning Experience only), `Communities` (Experience Cloud only), `VisualForce`. Use `All` unless there is a specific reason to restrict. |
-| `isApplicableToConnectSrc` | Yes | `true` if the domain is called via `fetch()`, `XMLHttpRequest`, or WebSocket. |
-| `isApplicableToFontSrc` | Yes | `true` if the domain serves font files (`.woff`, `.woff2`, `.ttf`, `.otf`). |
-| `isApplicableToFrameSrc` | Yes | `true` if the domain is loaded in an `<iframe>` or `<object>`. |
-| `isApplicableToImgSrc` | Yes | `true` if the domain serves images (`<img>`, CSS `background-image`, `<svg>`). |
-| `isApplicableToMediaSrc` | Yes | `true` if the domain serves audio or video (`<audio>`, `<video>`). |
-| `isApplicableToStyleSrc` | Yes | `true` if the domain serves CSS stylesheets (`<link rel="stylesheet">`). |
-
-**Reference:** [CspTrustedSite — Salesforce Object Reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_csptrustedsite.htm)
-
----
-
-## CSP directive mapping
-
-| CSP header directive | Metadata field | What it allows |
-|---------------------|----------------|----------------|
-| `connect-src` | `isApplicableToConnectSrc` | `fetch()`, `XMLHttpRequest`, WebSocket, `EventSource` |
-| `font-src` | `isApplicableToFontSrc` | `@font-face` sources |
-| `frame-src` | `isApplicableToFrameSrc` | `<iframe>`, `<frame>`, `<object>`, `<embed>` |
-| `img-src` | `isApplicableToImgSrc` | `<img>`, `background-image`, `favicon`, `<picture>` |
-| `media-src` | `isApplicableToMediaSrc` | `<audio>`, `<video>`, `<source>`, `<track>` |
-| `style-src` | `isApplicableToStyleSrc` | `<link rel="stylesheet">`, `@import` in CSS |
-
----
-
-## Common external domains and their directives
-
-Use this table as a quick reference when adding new domains:
-
-| Domain | connect-src | font-src | frame-src | img-src | media-src | style-src |
-|--------|:-----------:|:--------:|:---------:|:-------:|:---------:|:---------:|
-| `https://images.unsplash.com` | true | false | false | true | false | false |
-| `https://images.pexels.com` | true | false | false | true | false | false |
-| `https://videos.pexels.com` | true | false | false | false | true | false |
-| `https://fonts.googleapis.com` | true | false | false | false | false | true |
-| `https://fonts.gstatic.com` | true | true | false | false | false | false |
-| `https://avatars.githubusercontent.com` | true | false | false | true | false | false |
-| `https://api.open-meteo.com` | true | false | false | false | false | false |
-| `https://nominatim.openstreetmap.org` | true | false | false | false | false | false |
-| `https://tile.openstreetmap.org` | true | false | false | true | false | false |
-| `https://api.mapbox.com` | true | false | false | true | false | false |
-| `https://cdn.jsdelivr.net` | true | false | false | false | false | true |
-| `https://www.youtube.com` | false | false | true | true | false | false |
-| `https://player.vimeo.com` | false | false | true | false | false | false |
-| `https://res.cloudinary.com` | true | false | false | true | false | false |
-
----
-
-## Complete examples
-
-### Image CDN (Unsplash)
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>Unsplash_Images</fullName>
-    <description>Allow access to Unsplash image content for static app media</description>
-    <endpointUrl>https://images.unsplash.com</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>false</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>true</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>false</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
-### REST API (Open-Meteo weather)
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>Open_Meteo_API</fullName>
-    <description>Allow access to Open-Meteo weather forecast API</description>
-    <endpointUrl>https://api.open-meteo.com</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>false</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>false</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>false</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
-### Font provider (Google Fonts — requires two entries)
-
-Google Fonts needs two CSP entries because CSS is served from `fonts.googleapis.com` and font files from `fonts.gstatic.com`:
-
-**Entry 1: Stylesheets**
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>Google_Fonts</fullName>
-    <description>Allow access to Google Fonts stylesheets for custom typography</description>
-    <endpointUrl>https://fonts.googleapis.com</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>false</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>false</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>true</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
-**Entry 2: Font files**
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>Google_Fonts_Static</fullName>
-    <description>Allow access to Google Fonts static files for font loading</description>
-    <endpointUrl>https://fonts.gstatic.com</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>true</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>false</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>false</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
-### Map tiles (OpenStreetMap)
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>OpenStreetMap_Tiles</fullName>
-    <description>Allow access to OpenStreetMap tile images for map rendering</description>
-    <endpointUrl>https://tile.openstreetmap.org</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>false</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>true</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>false</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
-### Geocoding API (Nominatim)
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<CspTrustedSite xmlns="http://soap.sforce.com/2006/04/metadata">
-    <fullName>OpenStreetMap_Nominatim</fullName>
-    <description>Allow access to OpenStreetMap Nominatim geocoding API</description>
-    <endpointUrl>https://nominatim.openstreetmap.org</endpointUrl>
-    <isActive>true</isActive>
-    <context>All</context>
-    <isApplicableToConnectSrc>true</isApplicableToConnectSrc>
-    <isApplicableToFontSrc>false</isApplicableToFontSrc>
-    <isApplicableToFrameSrc>false</isApplicableToFrameSrc>
-    <isApplicableToImgSrc>false</isApplicableToImgSrc>
-    <isApplicableToMediaSrc>false</isApplicableToMediaSrc>
-    <isApplicableToStyleSrc>false</isApplicableToStyleSrc>
-</CspTrustedSite>
-```
-
----
-
-## Endpoint URL rules
-
-| Rule | Correct | Incorrect |
-|------|---------|-----------|
-| Must be HTTPS | `https://api.example.com` | `http://api.example.com` |
-| No trailing slash | `https://api.example.com` | `https://api.example.com/` |
-| No path | `https://api.example.com` | `https://api.example.com/v1/forecast` |
-| No port (unless non-standard) | `https://api.example.com` | `https://api.example.com:443` |
-| No wildcards | `https://api.example.com` | `https://*.example.com` |
-
-Each subdomain needs its own entry. For example, `fonts.googleapis.com` and `fonts.gstatic.com` are separate entries.
-
----
-
-## When a service requires multiple domains
-
-Some services split resources across multiple subdomains. Create one CSP Trusted Site per domain:
-
-| Service | Domains needed |
-|---------|---------------|
-| Google Fonts | `fonts.googleapis.com` (CSS) + `fonts.gstatic.com` (font files) |
-| Mapbox | `api.mapbox.com` (tiles/API) + `events.mapbox.com` (telemetry) |
-| YouTube embed | `www.youtube.com` (iframe) + `i.ytimg.com` (thumbnails) |
-| Cloudflare CDN | `cdnjs.cloudflare.com` (scripts/CSS) |
-
----
-
-## Troubleshooting CSP violations
-
-If the browser console shows a CSP error like:
-
-```
-Refused to load the image 'https://example.com/image.png' because it violates
-the following Content Security Policy directive: "img-src 'self' ..."
-```
-
-1. Extract the **blocked origin** from the URL (e.g. `https://example.com`).
-2. Identify the **directive** from the error message (e.g. `img-src` → `isApplicableToImgSrc`).
-3. Check if a CSP Trusted Site already exists for that origin.
-4. If not, create one using this skill.
-5. Deploy the metadata and refresh the page.
-
----
-
-## Common mistakes
-
-| Mistake | Fix |
-|---------|-----|
-| Including a path in `endpointUrl` | Use only the origin: `https://api.example.com` |
-| Adding trailing slash | Remove it: `https://api.example.com` not `https://api.example.com/` |
-| Using HTTP instead of HTTPS | Salesforce requires HTTPS. If the service only supports HTTP, it cannot be added. |
-| Forgetting `isApplicableToConnectSrc` | Most resources also need connect-src for redirects/preflight. Set to `true` by default. |
-| One entry for multiple subdomains | Each subdomain needs its own file (e.g. `api.example.com` and `cdn.example.com` are separate) |
-| File name doesn't match `fullName` | They must be identical (excluding the `.cspTrustedSite-meta.xml` extension) |

package/skills/generating-ui-bundle-site/SKILL.md

@@ -1,92 +0,0 @@
----
-name: generating-ui-bundle-site
-description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring site infrastructure. Use this skill when creating or configuring a Salesforce Digital Experience Site for hosting a UI bundle. Activate when files matching digitalExperiences/, networks/, customSite/, or DigitalExperienceBundle exist and need modification, or when the user wants to publish, host, or configure guest access for their app."
-metadata:
-  version: "1.0"
----
-
-# Digital Experience Site for React UI Bundles
-Create and configure Digital Experience Sites that host React UI bundles 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 UI bundle 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** | `All lowercase` (e.g., `mycommunity`) | User-provided, or convert siteName to all lowercase with alphanumeric characters only |
-| **appNamespace** | String | `namespace` in `sfdx-project.json` → `sf data query -q "SELECT NamespacePrefix FROM Organization" --target-org ${usernameOrAlias}` → default `c` |
-| **appDevName** | String | `UIBundle` metadata in the project → `sf data query -q "SELECT DeveloperName FROM UIBundle" --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
-Use available Salesforce metadata schema and field context for `Network`, `CustomSite`, `DigitalExperienceConfig`, and `DigitalExperienceBundle` to ensure each file uses valid structure.
-
-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) |
-
-For URL updates, see [update-site-urls.md](docs/update-site-urls.md).
-
-### Execution Note for Step 3: Load and use the docs
-- Agents MUST read the full contents of each docs/*.md file referenced in Step 3 before attempting to populate metadata fields.
-- Use your platform's file-read tool (for example, `read_file`) to load these files in full, then perform placeholder substitution for values in `{braces}` using the resolved properties from Step 1.
-- Files to load:
-  - `docs/configure-metadata-network.md`
-  - `docs/configure-metadata-custom-site.md`
-  - `docs/configure-metadata-digital-experience-config.md`
-  - `docs/configure-metadata-digital-experience-bundle.md`
-  - `docs/configure-metadata-digital-experience.md`
-- Read entire file contents, replace placeholders (e.g. `{siteName}`) with the resolved values, then use the expanded templates to populate the metadata XML/JSON content.
-  
-### Step 4: Do Not Modify Non-Templated Properties
-Do not modify any default property values for `Network`, `CustomSite`, `DigitalExperience`, `DigitalExperienceConfig`, or `DigitalExperienceBundle` metadata that are not expressed as variables wrapped in `{braces}`.
-
-## Verification Checklist
-Before deploying, confirm:
-
-- [ ] All five required properties are resolved
-- [ ] All metadata directories and files exist per the project structure
-- [ ] All metadata fields match the Step 3 templates with `{braces}` substituted only; no other default property values were added or changed
-- [ ] `appSpace` in `content.json` matches an existing `UIBundle` metadata record
-- [ ] Deployment validates successfully:
-```bash
-sf project deploy validate --metadata Network CustomSite DigitalExperienceConfig DigitalExperienceBundle DigitalExperience --target-org ${usernameOrAlias}
-```
-
-## Common Workflows
-
-### Updating Experience Site URLs
-
-**Use when** user wants to update or change site URLs (urlPathPrefix).
-
-**Steps**:
-- [ ] Read [update-site-urls.md](docs/update-site-urls.md) to understand the three-component architecture and URL update workflow
-- [ ] Follow the step-by-step workflow in the doc to update URLs consistently across all three components (DigitalExperienceConfig, Network, CustomSite)

package/skills/generating-ui-bundle-site/docs/configure-metadata-custom-site.md

@@ -1,41 +0,0 @@
-# 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-ui-bundle-site/docs/configure-metadata-digital-experience-bundle.md

@@ -1,17 +0,0 @@
-# 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-ui-bundle-site/docs/configure-metadata-digital-experience-config.md

@@ -1,21 +0,0 @@
-# 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>
-```