# Browser Simulator Routing

> Browser and simulator routing for authenticated web UI, isolated automation, and reusable device flows.

- Skill: `muhammedalkhudiry/browser-simulator-routing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add muhammedalkhudiry/browser-simulator-routing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/muhammedalkhudiry/browser-simulator-routing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: MuhammedAlkhudiry (https://skillmd.com/u/muhammedalkhudiry)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/muhammedalkhudiry/browser-simulator-routing

---


# Routing

Honor an explicitly named browser, device tool, or automation surface. Otherwise, choose one surface using the rules below and keep using it unless
the task requirements change.

Before browser automation, use a purpose-built connector, API, or CLI when the operation is semantic and does not require browser UI interaction.

Prefer text snapshots such as the accessibility tree, DOM, or device snapshot over screenshots. When a screenshot is required, capture it at 1x scale
and crop it to the region under inspection before attaching it.

## Browser

- When the task depends on existing user browser state, including a signed-in session, open tabs, or extensions, prefer `$chrome:control-chrome`. Use
  `$playwriter` when the user requests it, it is already active for the task, or Chrome control remains unavailable after its setup recovery and the
  user did not explicitly choose a browser. Read and follow the selected skill before acting.
- When browser UI interaction does not depend on existing user state, use `playwright-cli`. This includes local web-app testing and authentication
  created by the task inside an isolated Playwright profile. Read `playwright-cli --help`, then the narrowest relevant command help before acting.
- If an isolated Playwright task reaches a login that requires the user's existing session, switch to the existing-state route. Do not switch when the
  task or repository provides its own test authentication.
- If the user explicitly chose an unavailable browser surface, follow its setup recovery and then report the blocker. Do not silently substitute
  another browser.

## Simulator

- Use Maestro MCP when the user requests Maestro, an existing Maestro flow must be run or maintained, or the result must be reusable automation stored
  with the project. Use the MCP's live tools and documentation as the authority for supported actions and flow syntax.
- Use `$agent-device` for exploratory or one-off device interaction and for platforms outside the selected Maestro workflow. Read and follow the skill
  before acting.
- If the user explicitly chose an unavailable device surface, repair its setup when possible and then report the blocker. Do not silently substitute
  another surface.