Setup

Appium Setup Selection Workflow

Setup routing and selection

Select only the drivers named by the user or uniquely implied by their target. Treat each renma.continues-with item as a possible child Skill, not as execution order, priority, or automatic invocation.

Normalize common names such as uia2 to UiAutomator2. If no driver is named, infer it when the target maps uniquely in the table (for example, Firefox to Gecko or iOS to XCUITest). Ask before environment changes only when the target is missing or multiple routes remain plausible, such as an unspecified Android driver. Preserve every explicit selection without asking the user to choose again.

Required inputs

Resolve the selected drivers, global appium mode or explicitly requested local npx appium mode, target platforms, host OS, available devices, simulators, or browsers, permissions, and explicitly requested optional dependencies.

Workflow outline

1. Resolve the driver selection before changing the environment.
2. Hand each selected driver to its exact child Skill.
3. For multiple drivers, preserve the user's stated order. When the request states no order, choose and report an order that reuses shared host prerequisites, then execute the selected Skills one at a time. Metadata declaration order has no execution meaning.
4. Collect each child Skill's required doctor, helper, smoke, and evidence result without weakening its completion gate.

Setup selection safety and approval constraints

• Use global npm/Appium commands by default and local npx --no-install appium only when explicitly requested.
• Install only drivers selected from the user's named drivers or unambiguous target.
• Ask before optional FFmpeg or bundletool setup, third-party real-device tooling, privileged commands, browser installation, or authorization changes.
• Preserve working installations and prefer the smallest required change.

Completion criteria

Report passed only after every selected child Skill reaches its completion criteria. Otherwise report blocked, retaining each child's individual result, the evidence for every unresolved required check, and its next action. Optional warnings remain non-blocking.

Evidence boundary

Report the selected child Skills, command mode, each child Skill's pass/fail result, remaining optional items, and exact blockers. Attribute selection and execution exclusively to decisions made by the workflow body.

Self-Improvement Prompt

Before the final response, identify any missing, ambiguous, outdated, or retry-causing instruction in this selection workflow or a loaded child Skill. Report the asset path and proposed wording. Leave unrelated files unchanged.

Evidence

• Input: Set up Appium. Ask which driver or drivers are needed.
• Input: Set up UiAutomator2. Continue with skills/setup-uiautomator2/SKILL.md.
• Input: Set up Appium for Firefox. Infer Gecko and continue with skills/setup-gecko/SKILL.md without asking for a driver name.
• Input: Set up Appium for Android. Ask whether UiAutomator2 or Espresso is needed.
• Input: Set up UiAutomator2 and XCUITest. Continue with both selected child Skills and verify each independently.