Safari Setup Workflow
Routing
Prepare only the Appium Safari route on macOS. Use driver-specific official
guidance for an existing runtime failure after setup passes.
Required inputs
Confirm macOS as the host, desktop or simulator Safari target, global appium
mode or explicitly requested local npx appium mode, Safari automation state,
and permissions for authorization changes.
Workflow
- Load the global command profile by default or the local profile only when
explicitly requested.
- Load the macOS and Safari profiles, shared Appium setup basics, Safari
prerequisites, and Safari decision, installation, and smoke references.
- Run
node tools/appium/setup/scripts/check-safari-env.mjs --format summary --report auto; add
--appium-mode local only for explicitly requested local mode. Require
top-level summary.requiredOk: true.
Apply required fixes in technical dependency order and rerun affected checks.
If the gate remains unresolved, report blocked with evidence and the next
action. Load the matching example only when needed.
- Verify
appium driver doctor safari reports 0 required fixes needed, or
record not-supported and require the install, list, Safari, and smoke
gates instead. Use npx --no-install appium ... for the direct check in
local mode.
- Run
node tools/appium/setup/scripts/smoke-appium-server.mjs --driver safari --report auto;
add --appium-mode local only in local mode. Require
summary.requiredOk: true for server readiness, driver evidence, and
cleanup. The smoke reference documents target-specific options.
Safari setup safety and approval constraints
- Require macOS.
- Ask before privileged commands, browser installation, or enabling Safari
automation.
- Preserve the selected command mode and working Safari and driver
installations.
Completion criteria
safaridriver --version succeeds.
- Safari automation is enabled when needed and user-approved.
- Appium succeeds in the selected command mode and the installed list includes
safari.
- Doctor reports
0 required fixes needed when supported; unsupported doctor
behavior is reported and does not replace install, list, or smoke gates.
/status succeeds and logs list safari.
Evidence boundary
Report macOS and Safari versions, safaridriver evidence, Appium and driver
versions, helper and doctor summaries, authorization blockers, /status,
server driver evidence, and cleanup.
Self-Improvement Prompt
Before the final response, report any missing, ambiguous, outdated, or
retry-causing Safari setup instruction with its asset path and proposed
wording. Leave unrelated assets unchanged.
1---2name: setup-safari3description: Prepare and verify Appium Safari on macOS by validating Node/Appium, Safari and safaridriver prerequisites, driver installation, optional doctor behavior, authorization boundaries, and server smoke evidence. Use after the setup Skill selects Safari. Do not use for an existing Safari runtime failure after prerequisites pass.4---56# Safari Setup Workflow78## Routing910Prepare only the Appium Safari route on macOS. Use driver-specific official11guidance for an existing runtime failure after setup passes.1213## Required inputs1415Confirm macOS as the host, desktop or simulator Safari target, global `appium`16mode or explicitly requested local `npx appium` mode, Safari automation state,17and permissions for authorization changes.1819## Workflow20211. Load the global command profile by default or the local profile only when22 explicitly requested.232. Load the macOS and Safari profiles, shared Appium setup basics, Safari24 prerequisites, and Safari decision, installation, and smoke references.253. Run `node tools/appium/setup/scripts/check-safari-env.mjs --format summary --report auto`; add26 `--appium-mode local` only for explicitly requested local mode. Require27 top-level `summary.requiredOk: true`.28 Apply required fixes in technical dependency order and rerun affected checks.29 If the gate remains unresolved, report `blocked` with evidence and the next30 action. Load the matching example only when needed.314. Verify `appium driver doctor safari` reports `0 required fixes needed`, or32 record `not-supported` and require the install, list, Safari, and smoke33 gates instead. Use `npx --no-install appium ...` for the direct check in34 local mode.355. Run `node tools/appium/setup/scripts/smoke-appium-server.mjs --driver safari --report auto`;36 add `--appium-mode local` only in local mode. Require37 `summary.requiredOk: true` for server readiness, driver evidence, and38 cleanup. The smoke reference documents target-specific options.3940## Safari setup safety and approval constraints4142- Require macOS.43- Ask before privileged commands, browser installation, or enabling Safari44 automation.45- Preserve the selected command mode and working Safari and driver46 installations.4748## Completion criteria4950- `safaridriver --version` succeeds.51- Safari automation is enabled when needed and user-approved.52- Appium succeeds in the selected command mode and the installed list includes53 `safari`.54- Doctor reports `0 required fixes needed` when supported; unsupported doctor55 behavior is reported and does not replace install, list, or smoke gates.56- `/status` succeeds and logs list `safari`.5758## Evidence boundary5960Report macOS and Safari versions, `safaridriver` evidence, Appium and driver61versions, helper and doctor summaries, authorization blockers, `/status`,62server driver evidence, and cleanup.6364## Self-Improvement Prompt6566Before the final response, report any missing, ambiguous, outdated, or67retry-causing Safari setup instruction with its asset path and proposed68wording. Leave unrelated assets unchanged.