@salesforce/templates 66.5.5 → 66.5.6

package/lib/templates/project/reactb2x/_r_/skills/deploying-to-salesforce/SKILL.md

@@ -0,0 +1,226 @@
+---
+name: deploying-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.
+---
+
+# Deploying to Salesforce
+
+Guidance for AI agents deploying metadata to a Salesforce org or syncing with the org. **The order of operations is critical.** This skill codifies the exact sequence from `scripts/setup-cli.mjs` and documents **every Salesforce interaction**.
+
+## When to Use
+
+Invoke this skill whenever the task involves:
+
+- Deploying metadata (objects, permission sets, layouts, Apex, web applications)
+- Generating deploy commands or setup instructions
+- Fetching the GraphQL schema (`npm run graphql:schema`)
+- Running GraphQL codegen (`npm run graphql:codegen`)
+- Full org setup (login, deploy, permset, data, schema, build)
+- Any manual step that touches the Salesforce org
+
+## Canonical Sequence (from setup-cli.mjs)
+
+Execute steps in this **exact order**. Steps marked **(SF)** perform a Salesforce API or CLI interaction.
+
+### Step 1: Login — org authentication
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Check if org is connected | **(SF)** | `sf org display --target-org <alias> --json` |
+| If not connected: authenticate | **(SF)** | `sf org login web --alias <alias>` |
+
+- **Run when:** Org is not connected. **Omit when:** Org is already authenticated (check via `sf org display`).
+- All subsequent steps require an authenticated org.
+
+### Step 2: Webapp build — pre-deploy (required for entity deployment)
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Install dependencies | No | `npm install` (in each webapp dir) |
+| Build web app | No | `npm run build` (in each webapp dir) |
+
+- Produces `dist/` so `sf project deploy start` can deploy web application entities. Run **before** deploy when deploying web apps.
+- **Run when:** Deploying web apps AND (`dist/` does not exist OR webapp source has changed since last build). **Omit when:** Not deploying, or `dist/` is current and no source changes.
+
+### Step 3: Deploy metadata
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Deploy metadata | **(SF)** | See below |
+
+**Check for a manifest (package.xml) first.** Only use it if present:
+
+- **If `manifest/package.xml` (or `package.xml`) exists:** Deploy using the manifest:
+  ```bash
+  sf project deploy start --manifest manifest/package.xml --target-org <alias>
+  ```
+- **If no manifest exists:** Deploy all metadata from the project (packageDirectories in sfdx-project.json):
+  ```bash
+  sf project deploy start --target-org <alias>
+  ```
+
+Do not assume a manifest exists. Check the project root and common locations (e.g., `manifest/`, `config/`) before choosing the deploy command.
+
+- Deploys objects, layouts, permission sets, Apex classes, web applications, and all other metadata.
+- **Must complete successfully before schema fetch** — the schema reflects org state; custom objects/fields appear only after deployment.
+- **Run when:** Metadata has changed since last deploy, or never deployed. **Omit when:** No metadata changes and deploy has already run successfully.
+
+### Step 4: Post-deployment configuration — assign permissions and configure
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Assign permission set or group | **(SF)** | `sf org assign permset --name <name> --target-org <alias>` (works for both permsets and permset groups) |
+| Assign profile to user | **(SF)** | `sf data update record` or at user creation |
+| Other post-deploy config | **(SF)** | Varies (e.g., named credentials, connected apps, custom settings) |
+
+**Example commands:**
+
+```bash
+# Permission set (assigns to default user of target org)
+sf org assign permset --name Property_Management_Access --target-org myorg
+
+# Permission set group (same command; pass the group name)
+sf org assign permset --name My_Permset_Group --target-org myorg
+
+# Assign to a specific user
+sf org assign permset --name Property_Management_Access --target-org myorg --on-behalf-of user@example.com
+
+# Profile — update existing user's profile (requires ProfileId and User Id)
+sf data update record --sobject User --record-id <userId> --values "ProfileId=<profileId>" --target-org myorg
+
+# Profile — get ProfileId first
+sf data query --query "SELECT Id, Name FROM Profile WHERE Name='Standard User'" --target-org myorg
+```
+
+- **Deploying does not mean assigning.** Even after permission sets, permission set groups, and profiles are deployed to the org, they must be explicitly assigned or configured for users. Deployment makes them available; assignment/configuration grants access.
+- **Permission sets** — Assign to users so they have access to custom objects and fields. Required for GraphQL introspection to return the correct schema.
+- **Permission set groups** — Assign to users when using grouped permission sets.
+- **Profiles** — Ensure users have the correct profile; profile assignment may be done at user creation or via Setup.
+- **Other post-deploy configuration** — Named credentials, connected apps, custom settings, flow activation, and any metadata that requires manual configuration after deploy.
+- All of the above must exist in the org (deployed in Step 3).
+- **Run when:** Any permission set, permission set group, profile, or other post-deploy config was deployed or changed and not yet assigned/configured. **Omit when:** All required assignments and configuration are already in place.
+
+**Proactive behavior:** After a successful deploy, discover permission sets in the project (e.g., `force-app/main/default/permissionsets/*.permissionset-meta.xml`) and assign each one. Extract the API name from the filename (e.g., `Property_Management_Access.permissionset-meta.xml` → `Property_Management_Access`). If the user has not explicitly requested a full setup, you may ask: "Do you want me to assign the permission sets to your org?" — but do not skip this step silently; either run it or ask.
+
+### Step 5: Data — prepare and import (optional)
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Prepare unique fields | No | `node scripts/prepare-import-unique-fields.js --data-dir <dataDir>` |
+| Clean existing records | **(SF)** | `sf apex run --target-org <alias> --file <apex>` (per sobject, reverse plan order) |
+| Import records | **(SF)** | `sf apex run --target-org <alias> --file <apex>` (per batch) |
+
+- Only runs if `data/data-plan.json` and `data/` exist.
+- Delete runs in reverse plan order (children before parents).
+- Import uses Anonymous Apex with `Database.DMLOptions.duplicateRuleHeader.allowSave = true`.
+- **Run when:** Data plan exists AND (never imported OR data files or plan changed). **Omit when:** No data plan, or data already imported and unchanged.
+
+**Proactive behavior:** If `data/data-plan.json` and `data/` exist, you MUST ask the user: "Do you want me to import the sample data now? This will prepare unique fields, optionally clean existing records, and import data. Reply yes to proceed." Do not skip this step silently; either run it (after confirmation) or ask. Never import or clean without explicit user confirmation.
+
+### Step 6: GraphQL schema and codegen
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Install webapp deps | No | `npm install` (in webapp dir) |
+| Set default org | **(SF)** | `sf config set target-org <alias> --global` |
+| Fetch schema (introspection) | **(SF)** | `npm run graphql:schema` (from webapp dir) |
+| Generate types | No | `npm run graphql:codegen` (from webapp dir) |
+
+- `graphql:schema` performs GraphQL introspection against the org — a **Salesforce API call**.
+- Schema is written to `schema.graphql` at the SFDX project root.
+- Codegen reads the schema file locally; no Salesforce interaction.
+- **Run when:** Schema does not exist, OR metadata was deployed/changed since last schema fetch, OR permissions or post-deploy config was assigned since last schema fetch. **Omit when:** Schema exists and is current relative to org state.
+
+### Step 7: Webapp build (if not done in Step 2)
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Build web app | No | `npm run build` (in webapp dir) |
+
+- **Run when:** Build is needed (e.g., for dev server or deploy) AND (`dist/` does not exist OR webapp source has changed since last build). **Omit when:** `dist/` is current and no build needed.
+
+### Step 8: Dev server (optional)
+
+| Action | Salesforce interaction? | Command |
+|--------|-------------------------|---------|
+| Launch dev server | No | `npm run dev` (in webapp dir) |
+
+- **Run when:** User requests to launch the dev server. **Omit when:** Not requested.
+
+## Summary: All Salesforce Interactions (in order)
+
+1. `sf org display` — check org connection
+2. `sf org login web` — authenticate (if needed)
+3. `sf project deploy start` — deploy metadata
+4. `sf org assign permset` (permsets and permset groups) / profile assignment / other post-deploy config — assign permissions and configure
+5. `sf apex run` — delete existing data (if data plan)
+6. `sf apex run` — import data (if data plan)
+7. `sf config set target-org` — set default org for schema
+8. `npm run graphql:schema` — GraphQL introspection (Salesforce API)
+
+## Post-Deploy Checklist (MUST NOT SKIP)
+
+After **every successful metadata deploy**, the agent MUST address these before considering the task complete:
+
+1. **Permission sets** — Discover `force-app/main/default/permissionsets/*.permissionset-meta.xml`, extract API names, and assign each via `sf org assign permset --name <name> --target-org <alias>`. If unsure, ask: "Do you want me to assign the permission sets (e.g., Property_Management_Access, Tenant_Maintenance_Access) to your org?"
+2. **Data import** — If `data/data-plan.json` exists, ask: "Do you want me to import the sample data now? Reply yes to proceed." Do not import without confirmation.
+3. **Schema refetch** — Run `npm run graphql:schema` and `npm run graphql:codegen` from the webapp dir (required after deploy).
+
+Do not silently skip permission set assignment or data import. Either run them or ask the user.
+
+## Agent Decision Criteria
+
+Evaluate each step before running it. Ask:
+
+- **Has this step ever run before?** If not, it is likely needed.
+- **Have changes been made that require this step?** (e.g., metadata edits → deploy; deploy → schema refetch)
+- **Is the current state sufficient?** (e.g., org connected, schema exists and is current, permissions and post-deploy config assigned)
+
+Do not rely on CLI flags. Decide based on project state and what has changed.
+
+## Evaluation: When Each Step Touches Salesforce
+
+| Step | Salesforce interaction | Run when |
+|------|------------------------|----------|
+| 1. Login | Yes | Org not connected |
+| 2. Webapp build | No | Deploying web apps AND dist missing or source changed |
+| 3. Deploy | Yes | Metadata changed or never deployed |
+| 4. Post-deploy config | Yes | Permission sets, permset groups, profiles, or other config deployed/changed and not assigned |
+| 5. Data | Yes | Data plan exists AND (never imported OR data changed) |
+| 6. GraphQL | Yes (schema only) | Schema missing or metadata/permissions changed since last fetch |
+| 7. Webapp build | No | Build needed AND dist missing or source changed |
+| 8. Dev | No | User requests dev server |
+
+**Critical rule:** Steps 3 (deploy) and 4 (post-deploy config) must complete **before** step 6 (graphql:schema). The schema reflects the org state; running introspection too early yields an incomplete schema.
+
+## Schema Refetch Rule (CRITICAL)
+
+**After any metadata deployment**, you MUST re-run schema fetch and codegen:
+
+- New custom objects
+- New custom fields
+- New or updated permission sets
+- Any change to metadata that affects the GraphQL schema
+
+```bash
+# From webapp dir (force-app/main/default/webapplications/<appName>/)
+npm run graphql:schema
+npm run graphql:codegen
+```
+
+Do **not** assume the existing `schema.graphql` is current after metadata changes.
+
+## One-Command Setup (Reference)
+
+The project includes `scripts/setup-cli.mjs` which runs this sequence in batch. Use it when the user wants a full setup; otherwise, follow this skill and run only the steps that are needed based on current state.
+
+## Prohibited Actions
+
+- **Do not** run `npm run graphql:schema` before metadata is deployed — the schema will not include custom objects/fields
+- **Do not** skip schema refetch after deploying new metadata — types and queries will be out of sync
+- **Do not** assign permissions or configure before deploying — permission sets, permset groups, and profiles must exist in the org first
+- **Do not** run GraphQL introspection before assigning permissions — the user may lack FLS for custom fields
+
+## Related Skills
+
+- **using-salesforce-data** — Full data access workflow (GraphQL queries/mutations, REST APIs, schema exploration, webapp integration)

package/lib/templates/project/reactb2x/_r_/skills/{feature-react-file-upload-file-upload → implementing-file-upload}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: feature-react-file-upload-file-upload
+name: implementing-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.
 ---
 

package/lib/templates/project/{reactb2e/_r_/skills/webapp-features → reactb2x/_r_/skills/installing-webapp-features}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: webapp-features
-description: Search, describe, and install pre-built UI features (authentication, shadcn components, navigation, charts, 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.
+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.
 ---
 
 # webapps-features-experimental CLI — Agent Reference
 
-**Always check for an existing feature before building something yourself.** This CLI installs pre-built, tested feature packages into Salesforce webapps. Features range from foundational UI component libraries (shadcn/ui with Button, Card, Input, Table, etc.) to full-stack application capabilities like authentication (login, registration, password flows, session management, and Apex backend classes), global search, navigation menus, data visualization charts, GraphQL integrations, and Agentforce AI conversation UIs. Each feature ships as a complete implementation — including React components, context providers, route guards, and any required Salesforce server-side code — that already handles platform-specific concerns like Salesforce API integration, session management, and SFDX metadata structure. Building these from scratch is error-prone and unnecessary when a feature exists. **If no existing feature is found, ask the user before proceeding with a custom implementation — a relevant feature may exist under a different name or keyword.**
+**Always check for an existing feature before building something yourself.** This CLI installs pre-built, tested feature packages into Salesforce webapps. Features range from foundational UI component libraries (shadcn/ui with Button, Card, Input, Table, etc.) to full-stack application capabilities like authentication (login, registration, password flows, session management, and Apex backend classes), global search, navigation menus, GraphQL integrations, and Agentforce AI conversation UIs. Each feature ships as a complete implementation — including React components, context providers, route guards, and any required Salesforce server-side code — that already handles platform-specific concerns like Salesforce API integration, session management, and SFDX metadata structure. Building these from scratch is error-prone and unnecessary when a feature exists. **If no existing feature is found, ask the user before proceeding with a custom implementation — a relevant feature may exist under a different name or keyword.**
 
 ```
 npx @salesforce/webapps-features-experimental <command> [options]

package/lib/templates/project/reactb2x/_r_/skills/managing-agentforce-conversation-client/SKILL.md

@@ -0,0 +1,186 @@
+---
+name: managing-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.
+metadata:
+  author: ACC Components
+  version: 1.0.0
+  package: "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental"
+  sdk-package: "@salesforce/agentforce-conversation-client"
+  last-updated: 2025-03-18
+---
+
+# Managing Agentforce Conversation Client
+
+## Instructions
+
+### Step 1: Check if component already exists
+
+Search for existing usage across all app files (not implementation files):
+
+```bash
+grep -r "AgentforceConversationClient" --include="*.tsx" --include="*.jsx" --exclude-dir=node_modules
+```
+
+**Important:** Look for React files that import and USE the component (for example, shared shells, route components, or feature pages). Do NOT open files named `AgentforceConversationClient.tsx` or `AgentforceConversationClient.jsx` - those are the component implementation.
+
+**If found:** Read the file and check the current `agentId` value.
+
+**Agent ID validation rule (deterministic):**
+
+- Valid only if it matches: `^0Xx[a-zA-Z0-9]{15}$`
+- Meaning: starts with `0Xx` and total length is 18 characters
+
+**Decision:**
+
+- If `agentId` matches `^0Xx[a-zA-Z0-9]{15}$` and user wants to update other props → Go to Step 4 (update props)
+- If `agentId` is missing, empty, or does NOT match `^0Xx[a-zA-Z0-9]{15}$` → Continue to Step 2 (need real ID)
+- If not found → Continue to Step 2 (add new)
+
+### Step 2: Get agent ID
+
+If component doesn't exist or has an invalid placeholder value, ask user for their Salesforce agent ID.
+
+Treat these as placeholder/invalid values:
+
+- `"0Xx..."`
+- `"Placeholder"`
+- `"YOUR_AGENT_ID"`
+- `"<USER_AGENT_ID_18_CHAR_0Xx...>"`
+- Any value that does not match `^0Xx[a-zA-Z0-9]{15}$`
+
+Skip this step if:
+
+- Component exists with a real agent ID
+- User only wants to update styling or dimensions
+
+### Step 3: Canonical import strategy
+
+Use this import path by default in app code:
+
+```tsx
+import { AgentforceConversationClient } from "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental";
+```
+
+If the package is not installed, install it:
+
+```bash
+npm install @salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental
+```
+
+Only use a local relative import (for example, `./components/AgentforceConversationClient`) when the user explicitly asks to use a patched/local component in that app.
+
+Do not infer import path from file discovery alone. Prefer one consistent package import across the codebase.
+
+### Step 4: Add or update component
+
+**For new installations:**
+
+Add to the target React component file using the canonical package import:
+
+```tsx
+import { Outlet } from "react-router";
+import { AgentforceConversationClient } from "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental";
+
+export default function AgentChatHost() {
+  return (
+    <>
+      <Outlet />
+      <AgentforceConversationClient agentId="0Xx..." />
+    </>
+  );
+}
+```
+
+**Fallback note:** Use a local relative import only when the user explicitly requests patched/local component usage in that app.
+
+**For updates:**
+
+Read the file where component is used and modify only the props that need to change. Preserve all other props. Never delete and recreate.
+
+**Replacing placeholder values:**
+
+If the component has a placeholder agentId (e.g., `agentId="Placeholder"` or `agentId="0Xx..."`), replace it with the real agent ID:
+
+```tsx
+// Before (template with placeholder)
+<AgentforceConversationClient agentId="Placeholder" />
+
+// After (with real agent ID)
+<AgentforceConversationClient agentId="0Xx8X00000001AbCDE" />
+```
+
+### Step 5: Configure props
+
+**Available props (use directly on component):**
+
+- `agentId` (string, required) - Salesforce agent ID
+- `inline` (boolean) - `true` for inline mode, omit for floating
+- `width` (number | string) - e.g., `420` or `"100%"`
+- `height` (number | string) - e.g., `600` or `"80vh"`
+- `headerEnabled` (boolean) - Show/hide header
+- `styleTokens` (object) - For all styling (colors, fonts, spacing)
+- `salesforceOrigin` (string) - Auto-resolved
+- `frontdoorUrl` (string) - Auto-resolved
+
+**Examples:**
+
+Floating mode (default):
+
+```tsx
+<AgentforceConversationClient agentId="0Xx..." />
+```
+
+Inline mode with dimensions:
+
+```tsx
+<AgentforceConversationClient agentId="0Xx..." inline width="420px" height="600px" />
+```
+
+Styling with styleTokens:
+
+```tsx
+<AgentforceConversationClient
+  agentId="0Xx..."
+  styleTokens={{
+    headerBlockBackground: "#0176d3",
+    headerBlockTextColor: "#ffffff",
+    messageBlockInboundBackgroundColor: "#4CAF50",
+  }}
+/>
+```
+
+**For complex patterns,** consult `references/examples.md` for:
+
+- Sidebar containers and responsive sizing
+- Dark theme and advanced theming combinations
+- Inline without header, calculated dimensions
+- Complete host component examples
+
+**For styling:** For ANY color, font, or spacing changes, use `styleTokens` prop only. See `references/style-tokens.md` for complete token list and examples.
+
+**Common mistakes to avoid:** Consult `references/constraints.md` for:
+
+- Invalid props (containerStyle, style, className)
+- Invalid styling approaches (CSS files, style tags)
+- What files NOT to edit (implementation files)
+
+## Common Issues
+
+If component doesn't appear or authentication fails, see `references/troubleshooting.md` for:
+
+- Agent activation and deployment
+- Localhost trusted domains
+- Cookie restriction settings
+
+## Prerequisites
+
+Before the component will work, the following Salesforce settings must be configured by the user:
+
+**Cookie settings:**
+
+- Setup → My Domain → Disable "Require first party use of Salesforce cookies"
+
+**Trusted domains (required only for local development):**
+
+- Setup → Session Settings → Trusted Domains for Inline Frames → Add your domain
+  - Local development: `localhost:<PORT>` (e.g., `localhost:3000`)

package/lib/templates/project/reactb2x/_r_/skills/managing-agentforce-conversation-client/references/constraints.md

@@ -0,0 +1,134 @@
+# Constraints and Anti-Patterns
+
+This document lists all invalid approaches and patterns to avoid when working with AgentforceConversationClient.
+
+## Never Edit Implementation Files
+
+**CRITICAL: Only edit files where the component is USED, never the component implementation itself.**
+
+- ✅ **DO edit**: Any React files that import and use `<AgentforceConversationClient />` (for example, shared shells, route components, or feature pages)
+- ❌ **DO NOT edit**: AgentforceConversationClient.tsx, AgentforceConversationClient.jsx, index.tsx, index.jsx, or any files inside:
+  - `node_modules/@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental/src/`
+  - `packages/template/feature/feature-react-agentforce-conversation-client/src/`
+  - `src/components/AgentforceConversationClient.tsx` (patched templates)
+  - Any path containing `/components/AgentforceConversationClient.`
+
+**If you're reading a file named `AgentforceConversationClient.tsx`, you're in the wrong place. Stop and search for the USAGE instead.**
+
+## Invalid Props
+
+AgentforceConversationClient uses a flat prop API and does NOT accept these props:
+
+- ❌ `containerStyle` - Use `width` and `height` props directly instead
+- ❌ `style` - Use `styleTokens` for theming
+- ❌ `className` - Not supported
+- ❌ Any standard React div props - This wraps an embedded iframe, not a div
+
+**Why:** The component is a wrapper around an embedded iframe using Lightning Out 2.0. Standard React styling props don't apply.
+
+## Invalid Styling Approaches
+
+**CRITICAL: For ALL styling, theming, branding, or color changes - ONLY use `styleTokens` prop.**
+
+Never use these approaches:
+
+- ❌ Creating CSS files (e.g., `agent-styles.css`, `theme.css`)
+- ❌ Creating `<style>` tags or internal stylesheets
+- ❌ Using `style` attribute on the component
+- ❌ Using `className` prop
+- ❌ Inline styles
+- ❌ CSS modules
+- ❌ Styled-components or any CSS-in-JS libraries
+
+**Why:** The component controls its own internal styling through the `styleTokens` API. External CSS cannot reach into the embedded iframe.
+
+## Invalid Implementation Approaches
+
+Never do these:
+
+- ❌ Create custom chat UIs from scratch
+- ❌ Use third-party chat libraries (socket.io, WebSocket libraries, etc.)
+- ❌ Call `embedAgentforceClient` directly from `@salesforce/agentforce-conversation-client`
+- ❌ Build custom WebSocket or REST API chat implementations
+
+**Why:** The AgentforceConversationClient component is the official wrapper that handles authentication, Lightning Out 2.0 initialization, and all communication with Salesforce agents. Custom implementations will not work.
+
+## Invalid Update Patterns
+
+When updating an existing component:
+
+- ❌ Delete and recreate the component
+- ❌ Remove all props and start over
+- ❌ Copy the entire component to a new file
+
+**Why:** This loses configuration, introduces errors, and creates unnecessary diffs. Always update props in place.
+
+## Examples
+
+### ❌ Wrong - Using containerStyle
+
+```tsx
+<AgentforceConversationClient agentId="0Xx..." containerStyle={{ width: 420, height: 600 }} />
+```
+
+### ✅ Correct - Using width/height directly
+
+```tsx
+<AgentforceConversationClient agentId="0Xx..." width="420px" height="600px" />
+```
+
+### ❌ Wrong - Creating CSS file
+
+```css
+/* agent-styles.css */
+.agentforce-chat {
+  background: red;
+  color: white;
+}
+```
+
+```tsx
+import "./agent-styles.css";
+
+<AgentforceConversationClient className="agentforce-chat" />;
+```
+
+### ✅ Correct - Using styleTokens
+
+```tsx
+<AgentforceConversationClient
+  agentId="0Xx..."
+  styleTokens={{
+    headerBlockBackground: "red",
+    headerBlockTextColor: "white",
+  }}
+/>
+```
+
+### ❌ Wrong - Creating style tag
+
+```tsx
+<>
+  <style>{`.agent-chat { background: blue; }`}</style>
+  <AgentforceConversationClient agentId="0Xx..." />
+</>
+```
+
+### ✅ Correct - Using styleTokens
+
+```tsx
+<AgentforceConversationClient
+  agentId="0Xx..."
+  styleTokens={{
+    headerBlockBackground: "blue",
+  }}
+/>
+```
+
+### ❌ Wrong - Editing implementation file
+
+Reading or editing: `node_modules/@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental/src/AgentforceConversationClient.tsx`
+
+### ✅ Correct - Editing usage file
+
+Reading and editing: usage files where the component is imported and used (for example, `src/app.tsx`, a route component, or a feature page)