fix: resolve pr comments

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

@@ -83,7 +83,7 @@ Before doing anything else, note down the following properties from the local pr
 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/editing (custom/object pages)
+- [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

skills/salesforce-experience-lwr-site/docs/configure-content-view.md

@@ -1,6 +1,6 @@
 # Content Type: sfdc_cms__view
 
-**Use when** user explicitly requests creating a new page.
+**Use when** user explicitly requests creating a new page or editing an existing page.
 
 ## Table of Contents
 

skills/salesforce-experience-lwr-site/docs/configure-guest-sharing-rules.md

@@ -37,7 +37,7 @@ Use the `get_metadata_api_context` MCP tool:
 
 ## Critical Requirements
 
-1. **SharedTo Element**: Must use `<guestUser>{site Guest User's nickname}</guestUser>` where `{siteName}` is the Network name (not URL path prefix).
+1. **SharedTo Element**: Must use `<guestUser>{site Guest User's nickname}</guestUser>` (not URL path prefix).
 2. **includeHVUOwnedRecords**: Required field. Set to `false` unless records owned by high-volume site users should be included.
 3. **One XML file per object**: Put all rules for a given object in one file. Do not create additional.
 

skills/salesforce-experience-lwr-site/docs/handle-ui-components.md

@@ -2,55 +2,6 @@
 
 **Use when** adding/configuring components to be used in Experience site.
 
-## Table of Contents
-
-- Component Discovery Actions
-- Component Insertion
-
-## Component Discovery Actions
-
-Use these MCP actions in sequence when adding/configuring components.
-
-### 1. discoverUiComponents
-
-Find available OOTB components for page context.
-
-**viewType Values**:
-
-- Standard: `home`, `login-main`, `self-register`, `forgot-password`, `check-password`, `error`, `service-not-available`, `too-many-requests`
-- Record list: `list-{keyPrefix}` (standard) or `list-{ObjectApiName}` (custom)
-  - Example: `list-001` (Account), `list-Movie__c`
-- Record detail: `detail-{keyPrefix}` (standard) or `detail-{ObjectApiName}` (custom)
-  - Example: `detail-001` (Account), `detail-Movie__c`
-- Managed content: `managed-content-{contentType}`
-  - Example: `managed-content-sfdc_cms__news`
-
-**Returns**: `componentDefinitions` array with `definition` (FQN), `label`, `description`.
-
-### 2. getUiComponentSchemas
-
-Get JSON schemas for component attributes.
-
-**Returns**: `componentSchemas` with required/optional properties and data source references.
-
-### 3. getDataSourceValues
-
-Get available values for attribute data sources (picklists, fields, etc.).
-
-**Returns**: `dataSourceValues` map.
-
-### Workflow
-
-1. Call `discoverUiComponents` to find OOTB components
-2. Select component(s) matching requirements
-3. Call `getUiComponentSchemas` for attribute schemas
-4. Call `getDataSourceValues` for data source attributes
-5. Configure components with valid values
-
-**Prioritize OOTB components** - only create custom if no OOTB option fits.
-
----
-
 ## Component Insertion
 
 Insert custom Lightning Web Components (LWC) into views.