@salesforce/afv-skills 1.3.0 → 1.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.3.0",
+  "version": "1.5.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [
@@ -11,14 +11,15 @@
     "registry": "https://registry.npmjs.org"
   },
   "devDependencies": {
-    "@salesforce/webapp-template-app-react-sample-b2e-experimental": "1.109.1",
-    "@salesforce/webapp-template-app-react-sample-b2x-experimental": "1.109.1",
+    "@salesforce/webapp-template-app-react-sample-b2e-experimental": "^1.112.7",
+    "@salesforce/webapp-template-app-react-sample-b2x-experimental": "^1.112.7",
+    "@types/js-yaml": "^4.0.9",
+    "js-yaml": "^4.1.1",
     "tsx": "^4.21.0"
   },
   "scripts": {
     "validate:skills": "tsx scripts/validate-skills.ts",
     "sync-react-b2e-sample": "node scripts/sync-react-b2e-sample.js",
-    "sync-react-b2x-sample": "node scripts/sync-react-b2x-sample.js",
-    "sync-webapp-skills": "node scripts/sync-webapp-skills.js"
+    "sync-react-b2x-sample": "node scripts/sync-react-b2x-sample.js"
   }
 }

package/skills/building-webapp-data-visualization/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: building-webapp-data-visualization
-description: Adds data visualization components (charts, stat cards, KPI metrics) to React pages using Recharts. Use when the user asks to add a chart, graph, donut chart, pie chart, bar chart, stat card, KPI metric, dashboard visualization, or analytics component to the web application.
+description: "Adds data visualization components (charts, stat cards, KPI metrics) to React pages using Recharts. Use when the user asks to add a chart, graph, donut chart, pie chart, bar chart, stat card, KPI metric, dashboard visualization, or analytics component to the web application."
 ---
 
 # Data Visualization

package/skills/building-webapp-react-components/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: building-webapp-react-components
-description: Use when editing any React code in the web application — creating or modifying components, pages, layout, headers, footers, or any TSX/JSX files. Follow this skill for add component, add page, header/footer, and general React UI implementation patterns (shadcn UI and Tailwind CSS).
+description: "Use when editing any React code in the web application — creating or modifying components, pages, layout, headers, footers, or any TSX/JSX files. Follow this skill for add component, add page, header/footer, and general React UI implementation patterns (shadcn UI and Tailwind CSS)."
 ---
 
 # React Web App (Components, Pages, Layout)

package/skills/configuring-webapp-csp-trusted-sites/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: configuring-webapp-csp-trusted-sites
-description: Creates Salesforce CSP Trusted Site metadata when adding external domains. Use when the user adds an external API, CDN, image host, font provider, map tile server, or any third-party URL that the web application needs to load resources from — or when a browser console shows a CSP violation error.
+description: "Creates Salesforce CSP Trusted Site metadata when adding external domains. Use when the user adds an external API, CDN, image host, font provider, map tile server, or any third-party URL that the web application needs to load resources from — or when a browser console shows a CSP violation error."
 ---
 
 # CSP Trusted Sites

package/skills/configuring-webapp-metadata/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: configuring-webapp-metadata
-description: Use this skill when configuring web application metadata structure, webapplication.json, or bundle organization. Covers WebApplication bundle layout, meta XML, build output directory, and webapplication.json settings.
+description: "Use this skill when configuring web application metadata structure, webapplication.json, or bundle organization. Covers WebApplication bundle layout, meta XML, build output directory, and webapplication.json settings."
 ---
 
 # WebApplication Requirements
@@ -53,7 +53,7 @@ Applies to:
 
 Reject:
 - backslashes
-- leading `\`
+- leading `/` or `\`
 - `..` segments
 - null or control characters
 - globs: `*`, `?`, `**`

package/skills/creating-webapp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: creating-webapp
-description: Use this skill when creating or setting up a new SFDX React web application. Covers first steps, npm install, skills-first protocol, deployment order, and core web app rules.
+description: "Use this skill when creating or setting up a new SFDX React web application. Covers first steps, npm install, skills-first protocol, deployment order, and core web app rules."
 paths:
   - "**/webapplications/**/*"
 ---
@@ -111,7 +111,7 @@ Apps run behind dynamic base paths. Router navigation (`<Link to>`, `navigate()`
 
 ## Module Restrictions
 
-React apps must NOT import Salesforce platform modules like `lightning/*` or `@wire` (LWC-only). For data access, invoke the **accessing-data** skill.
+React apps must NOT import Salesforce platform modules like `lightning/*` or `@wire` (LWC-only). For data access, invoke the **using-salesforce-data** skill.
 
 # Frontend Aesthetics
 
@@ -138,4 +138,3 @@ Only stop when:
 - All checklist items are completed and quality gates pass, or
 - A blocking error cannot be resolved after reasonable remediation, or
 - The user explicitly asks to pause.
-

package/skills/deploying-webapp-to-salesforce/SKILL.md

@@ -1,8 +1,6 @@
 ---
 name: deploying-webapp-to-salesforce
-description: Enforces the correct order for deploying metadata, assigning permission sets, and fetching GraphQL schema. Use for ANY deployment to a Salesforce org — webapps, LWC, Aura, Apex, metadata, schema fetch, or org sync. Codifies setup-cli.mjs.
-paths:
-  - "**/*"
+description: "Enforces the correct order for deploying metadata, assigning permission sets, and fetching GraphQL schema. Use for ANY deployment to a Salesforce org — webapps, LWC, Aura, Apex, metadata, schema fetch, or org sync. Codifies setup-cli.mjs."
 ---
 
 # Deploying to Salesforce
@@ -225,5 +223,4 @@ The project includes `scripts/setup-cli.mjs` which runs this sequence in batch.
 
 ## Related Skills
 
-- **exploring-graphql-schema** — Schema exploration (grep-only) after schema exists
-- **using-graphql** — Full GraphQL workflow (explore, query, codegen, lint)
+- **using-salesforce-data** — Full data access workflow (GraphQL queries/mutations, REST APIs, schema exploration, webapp integration)

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

@@ -1,6 +1,6 @@
 ---
 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.
+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."
 ---
 
 ## When to Use This Skill

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

@@ -1,6 +1,6 @@
 ---
 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.
+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."
 ---
 
 ## When to Use This Skill

package/skills/generating-custom-lightning-type/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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.
+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."
 ---
 
 ## When to Use This Skill

package/skills/generating-custom-object/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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.
+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."
 ---
 
 ## When to Use This Skill

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

@@ -1,6 +1,6 @@
 ---
 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.
+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."
 ---
 
 ## When to Use This Skill

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

@@ -1,12 +1,17 @@
 ---
 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.
+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).
 
+## IMPORTANT!!
+
+Right after loading this skill, you MUST copy the selected workflows/steps to your plan as a TODO checklist and work on each of the item carefully to ensure correctness.
+You MUST load the relevant reference docs even though they may live outside of user's project folder.
+
 ## Table of Contents
 
 - When to Use
@@ -33,8 +38,8 @@ When working with Experience LWR sites:
 ## 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.
+2. **MUST ALWAYS** load the relevant reference docs before doing anything.
+3. **MUST 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
@@ -71,7 +76,7 @@ Before doing anything else, note down the following properties from the local pr
 | `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__brandingSet` | Brand colors, fonts, and styling tokens | Required; defines site-wide styling. Use to create or edit existing branding sets |
 | `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 |
@@ -79,9 +84,14 @@ Before doing anything else, note down the following properties from the local pr
 
 **Important:** Creating any new pages require BOTH `sfdc_cms__route` AND `sfdc_cms__view`.
 
+#### Object Pages
+
+Object Pages are dedicated pages used to display and manage record-level data for a specific Salesforce entity/object. For example, an custom object "Car" should have "Car_Detail", "Car_List", and "Car_Related_list" views.
+
 ## References
 
 Reference docs within the skill directory. Note that these are **local** and not MCP.
+Before doing anything, you **MUST ALWAYS** load them first if they match user intent.
 
 - [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)
@@ -111,32 +121,46 @@ Reference docs within the skill directory. Note that these are **local** and not
 
 **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
+- [ ] MUST read [configure-content-route.md](docs/configure-content-route.md)
+- [ ] MUST read [configure-content-view.md](docs/configure-content-view.md)
+- [ ] MUST read [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
 
 ### 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:
+- [ ] MUST read [handle-ui-components.md](docs/handle-ui-components.md) to add LWCs to LWR sites.
+- [ ] MUST read [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md) to handle id generation
+- [ ] MUST read [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 Page Layouts / Container Components
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] MUST read [handle-ui-components.md](docs/handle-ui-components.md)
+
 ### 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).
+- [ ] Check with user whether this new theme layout reuses an existing theme layout component or requires a new one.
+- [ ] MUST read [handle-ui-components.md](docs/handle-ui-components.md) if creating a new theme layout component.
+- [ ] MUST read [configure-content-themeLayout.md](docs/configure-content-themeLayout.md).
+- [ ] MUST read [configure-content-view.md](docs/configure-content-view.md) if need to apply theme layout to pages
+
+### Applying/Setting Theme Layouts
+
+**Steps** (Follow the steps sequentially. Do not skip any step before proceeding):
+
+- [ ] MUST read [configure-content-view.md](docs/configure-content-view.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.
+- [ ] MUST read [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
 
@@ -145,8 +169,8 @@ Reference docs within the skill directory. Note that these are **local** and not
 **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
+- [ ] MUST read 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).
+- [ ] MUST 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:
@@ -162,9 +186,11 @@ Reference docs within the skill directory. Note that these are **local** and not
 }
 ```
 
-### Retrieving Site URLs After Deployment
+### Retrieving Site Preview and Builder URLs After Deployment
+
+**Use when** user requests to preview a site, access a builder site, or after successfully deploying a site.
 
-After successfully deploying the site using `sf project deploy`, use the `execute_metadata_action` MCP tool to get the preview and builder URLs:
+Use the `execute_metadata_action` MCP tool to get the preview and builder URLs:
 
 ```json
 {

package/skills/generating-experience-lwr-site/docs/configure-content-brandingSet.md

@@ -6,6 +6,7 @@
 
 - Core Principles
 - Generation Guidelines
+- Editing Existing Branding Sets
 - Branding Property Patterns
 
 ## Core Principles
@@ -58,7 +59,11 @@ The `content.json` file must contain:
 - `title`: **Required**. Human-readable display title (e.g., Branding Set).
   - Maximum length is **100 characters**.
   - Must be **unique** within the space's brandingSet content items.
-- `contentBody`: Include all `required` properties from `schemaDefinition`. Use `examplesOfContentType` for reference.
+- `contentBody`: Include all `required` properties from `schemaDefinition`. 
+  1. **Seed**: Always call `execute_metadata_action` with `shouldIncludeExamples: true`. Copy the *entire* example object from `examplesOfContentType[0]` into `content.json`. **NEVER** start from a minimal stub.
+  2. **Recalculate (CRITICAL STOP)**: You MUST stop and perform explicit changes for dependent tokens BEFORE generating JSON.
+    - [] Refer to "Branding Property Patterns" for detailed calculations.
+
   - `brandingSetType`: Represents whether the color palette is for the entire site or a specific section.
     - `APP`: The branding set applies to the entire site. There can be only one branding set of this type.
     - `SCOPED`: A `SCOPED` branding set can be applied only to a section component for granular overrides.
@@ -70,10 +75,6 @@ The `content.json` file must contain:
     - **Patterns**: See the "Branding Property Patterns" section for details on value relationships.
 - `urlName`: Lowercase with hyphens (e.g., `branding-set`)
 
-**Rules**:
-
-- Before any actions, *always* call `execute_metadata_action` to get the full schema and examples per the skill document.
-
 ### 4. Naming Conventions Summary
 
 | Field | Format | Example |
@@ -84,9 +85,18 @@ The `content.json` file must contain:
 
 ### 5. Generation Checklist
 
-- [ ] Directory and `_meta.json` follow naming conventions (1, 2)
-- [ ] `content.json` has all required fields (3)
+- [ ] Directory and `_meta.json` follow naming conventions
+- [ ] `content.json` has all required fields
 - [ ] `contentBody` follows the schema provided by `execute_metadata_action`
+- [ ] **STOP AND VERIFY**: `contentBody.values` honors all **Branding Property Patterns** defined below and explicitly recalculated and updated all dependent tokens based on any token updates requested by the user.
+
+## Editing Existing Branding Sets
+
+Use this section when modifying existing branding sets under the `sfdc_cms__brandingSet` directory.
+
+### Editing Checklist
+
+- [ ] Ensure all modified branding properties honor the **Branding Property Patterns** defined below.
 
 ## Branding Property Patterns
 

package/skills/generating-experience-lwr-site/docs/configure-content-themeLayout.md

@@ -72,6 +72,7 @@ The `content.json` file must contain:
 - `contentBody`: Include all `required` properties from `schemaDefinition`. Use `examplesOfContentType` for reference.
 - Do not add additional fields.
 - `urlName`: URL identifier (lowercase, words separated by dashes e.g., "scoped-header-and-footer")
+- `contentBody.compnent.definition`: The actual theme layout component that displays/renders the layout and includes theme region components.
 
 **Rules**:
 
@@ -130,7 +131,7 @@ When generating a new theme layout, ensure:
 - [ ] `urlName` uses lowercase with hyphens (V)
 - [ ] `title` is human-readable (V)
 - [ ] `sfdc_cms__theme/[THEME_API_NAME]/content.json` updated by appending a new `contentBody.layouts` mapping (VI)
-- [ ] **CRITICAL**: Complete all the UUID generation steps. See `docs/handle-component-and-region-ids.md`
+- [ ] **CRITICAL**: Complete all the UUID generation steps. See [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
 
 ## Purpose B: Editing Existing Theme Layouts
 

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

@@ -49,7 +49,7 @@ The `_meta.json` file must contain:
 
 ### Theme Layout Type (All Views)
 
-The `contentBody.themeLayoutType` field specifies which theme layout to use for the view.
+The `contentBody.themeLayoutType` field specifies which theme layout to use for the view. There can only be one per view.
 
 - **Default**: `"Inner"` - Use this default if the user does not specify a layout OR if the lookup fails to find a matching layoutType
 - **Lookup**: To find valid values:
@@ -126,7 +126,7 @@ The route's `activeViewId` must match the view's directory name exactly.
 - [ ] Directory and `_meta.json` follow structure (see Directory Structure, _meta.json Structure)
 - [ ] `content.json` has all required fields (A.1)
 - [ ] Component structure correct with both regions (A.1)
-- [ ] **CRITICAL**: Complete all the UUID generation steps. see `docs/handle-component-and-region-ids.md`
+- [ ] **CRITICAL**: Complete all the UUID generation steps. see [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
 - [ ] `viewType` matches route's `routeType` (CRITICAL)
 
 ### PART B: OBJECT PAGES
@@ -218,7 +218,7 @@ The route's `activeViewId` must match the view's directory name exactly. The `vi
 - [ ] `viewType` matches route's `routeType` for all three views (CRITICAL)
 - [ ] Component structure correct with both regions (see A.1)
 - [ ] SEO assistant configured correctly per view type (B.4)
-- [ ] **CRITICAL**: Complete both UUID generation steps. see `docs/handle-component-and-region-ids.md`
+- [ ] **CRITICAL**: Complete both UUID generation steps. see [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md)
 
 ## Purpose B: Editing Existing Views
 

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

@@ -1,6 +1,6 @@
 ---
 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."
+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

package/skills/generating-flexipage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-flexipage
-description: Use this skill when users need to create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger when users mention RecordPage, AppPage, HomePage, Lightning pages, page layouts, adding components to pages, or page customization. Also use when users say things like "create a Lightning page", "add a component to a page", "customize the record page", "generate a FlexiPage", or when they're working with FlexiPage XML files and need help with components, regions, or deployment errors. Always use this skill for any FlexiPage-related work, even if they just mention "page" in the context of Salesforce.
+description: "Use this skill when users need to create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger when users mention RecordPage, AppPage, HomePage, Lightning pages, page layouts, adding components to pages, or page customization. Also use when users say things like \"create a Lightning page\", \"add a component to a page\", \"customize the record page\", \"generate a FlexiPage\", or when they're working with FlexiPage XML files and need help with components, regions, or deployment errors. Always use this skill for any FlexiPage-related work, even if they just mention \"page\" in the context of Salesforce."
 ---
 
 ## When to Use This Skill

package/skills/generating-flow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-flow
-description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.
+description: "Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as \"when a record is created\", \"trigger daily at\", \"send an email when\", \"update the field when\", \"automate\", \"workflow\", or \"flow XML/metadata\". This is the only skill for Salesforce Flow generation."
 ---
 
 ## Goal

package/skills/generating-fragment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-fragment
-description: Use this skill when users need to create or edit Salesforce Fragments (reusable UI pieces). Trigger when users mention fragments, UEM blocks, reusable UI templates, structured rendering across Slack/Mobile/LEX, or block-based layouts. Also use when users want to create unified experience components. Always use this skill for any fragment work.
+description: "Use this skill when users need to create or edit Salesforce Fragments (reusable UI pieces). Trigger when users mention fragments, UEM blocks, reusable UI templates, structured rendering across Slack/Mobile/LEX, or block-based layouts. Also use when users want to create unified experience components. Always use this skill for any fragment work."
 ---
 
 ## When to Use This Skill

package/skills/generating-list-view/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-list-view
-description: Use this skill when users need to create, generate, or validate Salesforce List View metadata. Trigger when users mention list views, filtered record lists, creating views, setting up record columns, filtering records by criteria, or ask about list view visibility. Also use when users say things like "I need a view that shows...", "filter records by...", "create a list view for...", or when they're working with ListView XML files and need validation or troubleshooting.
+description: "Use this skill when users need to create, generate, or validate Salesforce List View metadata. Trigger when users mention list views, filtered record lists, creating views, setting up record columns, filtering records by criteria, or ask about list view visibility. Also use when users say things like \"I need a view that shows...\", \"filter records by...\", \"create a list view for...\", or when they're working with ListView XML files and need validation or troubleshooting."
 ---
 
 ## When to Use This Skill

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

@@ -1,6 +1,6 @@
 ---
 name: generating-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.
+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

package/skills/generating-validation-rule/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-validation-rule
-description: Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work.
+description: "Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work."
 ---
 
 ## When to Use This Skill

package/skills/implementing-webapp-file-upload/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: implementing-webapp-file-upload
-description: Add file upload functionality to React webapps with progress tracking and Salesforce ContentVersion integration. Use when the user wants to upload files, attach documents, handle file input, create file dropzones, track upload progress, or link files to Salesforce records. This feature provides programmatic APIs ONLY — no components or hooks are exported. Build your own custom UI using the upload() API. ALWAYS use this feature instead of building file upload from scratch with FormData or XHR.
+description: "Add file upload functionality to React webapps with progress tracking and Salesforce ContentVersion integration. Use when the user wants to upload files, attach documents, handle file input, create file dropzones, track upload progress, or link files to Salesforce records. This feature provides programmatic APIs ONLY — no components or hooks are exported. Build your own custom UI using the upload() API. ALWAYS use this feature instead of building file upload from scratch with FormData or XHR."
 ---
 
 # File Upload API (workflow)

package/skills/installing-webapp-features/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: installing-webapp-features
-description: Search, describe, and install pre-built UI features (authentication, shadcn components, navigation, search, GraphQL, Agentforce AI) into Salesforce webapps. Use this when the user wants to add functionality to a webapp, or when determining what salesforce-provided features are available — whether prompted by the user or on your own initiative. Always check for an existing feature before building from scratch.
+description: "Search, describe, and install pre-built UI features (authentication, shadcn components, navigation, search, GraphQL, Agentforce AI) into Salesforce webapps. Use this when the user wants to add functionality to a webapp, or when determining what salesforce-provided features are available — whether prompted by the user or on your own initiative. Always check for an existing feature before building from scratch."
 ---
 
 # webapps-features-experimental CLI — Agent Reference

package/skills/managing-webapp-agentforce-conversation-client/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: managing-webapp-agentforce-conversation-client
-description: Adds or modifies AgentforceConversationClient in React apps (.tsx or .jsx files). Use when user says "add chat widget", "embed agentforce", "add agent", "add chatbot", "integrate conversational AI", or asks to change colors, dimensions, styling, or configure agentId, width, height, inline mode, or styleTokens for travel agent, HR agent, employee agent, or any Salesforce agent chat.
+description: "Adds or modifies AgentforceConversationClient in React apps (.tsx or .jsx files). Use when user says \"add chat widget\", \"embed agentforce\", \"add agent\", \"add chatbot\", \"integrate conversational AI\", or asks to change colors, dimensions, styling, or configure agentId, width, height, inline mode, or styleTokens for travel agent, HR agent, employee agent, or any Salesforce agent chat."
 metadata:
   author: ACC Components
   version: 1.0.0

package/skills/trigger-refactor-pipeline/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: trigger-refactor-pipeline
-description: Refactor Salesforce triggers into handler patterns with automated test generation and deployment. Use when modernizing legacy triggers with DML/SOQL in loops or inconsistent patterns.
+description: "Refactor Salesforce triggers into handler patterns with automated test generation and deployment. Use when modernizing legacy triggers with DML/SOQL in loops or inconsistent patterns."
 license: Apache-2.0
 compatibility: Requires Salesforce CLI, Python 3.9+
 metadata: