agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/hermes-mobile-verification.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

Mandatory Hermes Mobile verification after edits — never wait for user to ask for E2E

The file

We split this hermes-mobile-verification.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When editing anything under hermes-mobile/:

    line 10
  2. Very specific:

    Run unit tests in the same turn: cd hermes-mobile && npm test -- --no-coverage --watchman=false

    line 12
  3. Very specific:

    Read hermes-mobile/docs/proofs/continuous/latest.json before claiming chat/UI is fixed.

    line 18

≈ “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
hermes-mobile-verification.mdc
---
description: Mandatory Hermes Mobile verification after edits — never wait for user to ask for E2E
globs:
  - hermes-mobile/**
alwaysApply: false
---

# Hermes Mobile verification

When editing anything under `hermes-mobile/`:

1. Run unit tests in the same turn: `cd hermes-mobile && npm test -- --no-coverage --watchman=false`
2. Trigger autonomous E2E (do not tell the user to run Maestro):
   ```bash
   launchctl kickstart -k "gui/$(id -u)/com.igor.hermes-mobile-continuous-e2e" 2>/dev/null \
     || (cd hermes-mobile && npm run e2e:continuous:once)
   ```
3. Read `hermes-mobile/docs/proofs/continuous/latest.json` before claiming chat/UI is fixed.
4. Phone setup: `node tools/hermes-mobile-pair.js` when `adb devices` shows a device — never manual Settings steps.
5. **Brand-new user mindset** — every test assumes a stranger: no adb, no dev backdoor, release build, realistic network. See [hermes-mobile-real-users.mdc](./hermes-mobile-real-users.mdc).

Full contract: [hermes-mobile/AGENTS.md](../../hermes-mobile/AGENTS.md).

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.