---
id: "a5c51e75-6fce-446c-8294-542dc81e3e3e"
name: "salesforce.* / force.com"
micro_summary: "Salesforce browser automation hub for Lightning Setup, embedded Classic/Aloha pages, and sandbox org UI flows."
status: "in_progress"
see_also: []
scope: "Salesforce browser automation hub for Lightning Setup, embedded Classic/Aloha pages, sandbox org UI flows, and policy-required Setup UI workflows that CLI cannot operate."
---
## Role

Browser-harness tactics for Salesforce web UI automation. This hub owns page structure, selectors, shadow DOM/iframe traps, and Setup UI flows. Salesforce CLI/API strategy lives in the Salesforce Metadata tree; this node owns only browser interaction patterns.

## Skills vs helpers decision

Use this SiftText browser-harness subtree as the Salesforce UI skills hub. Add browser-harness helper functions only for stable mechanical primitives (for example, reading or clicking inside the Lightning Setup Aloha iframe). Do not encode ticket-specific or business workflows as helpers. Pi skill files can later act as routing glue that tells agents which nodes to read first, but they should not be the source of truth for volatile Salesforce UI behavior.