agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/agent-device.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

Use Callstack agent-device for Hermes Mobile device automation (connection crisis, Tailscale, fresh-user UI)

The file

We split this agent-device.mdc into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use agent-device for app/device automation on Hermes Mobile — not as a generic shell.

    line 10
  2. Distinctive:

    Before planning device work:

    line 12
  3. Very specific:

    If missing: bash scripts/install-agent-device.sh (pins 0.19.3 to match hermes-mobile/package.json).

    line 20
  4. Very specific:

    Prefer open -> snapshot -i -> act -> re-snapshot -> verify -> close.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
agent-device.mdc
---
description: Use Callstack agent-device for Hermes Mobile device automation (connection crisis, Tailscale, fresh-user UI)
alwaysApply: false
globs:
  - hermes-mobile/**/*
---

# agent-device (Callstack)

Use **agent-device** for app/device automation on Hermes Mobile — not as a generic shell.

Before planning device work:

```bash
export PATH="$HOME/.npm-global/bin:$PATH"
agent-device --version
agent-device help workflow
```

If missing: `bash scripts/install-agent-device.sh` (pins `0.19.3` to match `hermes-mobile/package.json`). Do **not** run `npx -y agent-device@latest`.

## When to use what

| Tool | Use for |
|------|---------|
| **agent-device** | Exploratory QA, connection/Tailscale/fresh-user UI proofs, screenshots + a11y snapshots, RN debugging (`help react-native`) |
| **Maestro** (`npm run e2e:*`, continuous LaunchAgent) | Deterministic CI / ship-guard / chat-send-persistence; `latest.json` is the ship gate |
| **adb** / `hermes-mobile-pair.js` | Install, pair, `adb reverse`, package clear — not primary UI inspection |

Full matrix: [hermes-mobile/docs/AGENT-DEVICE.md](../../hermes-mobile/docs/AGENT-DEVICE.md).

## Hermes loop

```bash
agent-device open com.iganapolsky.hermesmobile --platform android --serial "$SERIAL" --session hermes
agent-device press 'label="Hermes"' --session hermes --settle
agent-device snapshot --session hermes
agent-device close --session hermes
```

Or: `bash hermes-mobile/scripts/agent-device-connection-proof.sh`

Prefer `open -> snapshot -i -> act -> re-snapshot -> verify -> close`. Keep mutating commands on one session serial. Chat composer automation must type only **`make money today`**.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.