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

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

Hermes Mobile is a real-user product — never dogfood-only assumptions in tests or UX

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Before claiming fixed, shipped, or "works on device", assume the tester has:

    line 16
  2. Distinctive:

    Never paired before; no saved gateway profiles.

    line 18
  3. Distinctive:

    No knowledge of Mac hostname, tunnel URLs, or relay codes

    line 21
  4. Very specific:

    Do not pass tests that only work because Igor's Mac is plugged in, adb reverse is set, or developerLeashUnlock is on.

    line 24
  5. Very specific:

    Tests: Run npm run test:ci; onboarding copy guarded by freshUserOnboarding.test.ts, FreshUserOnboardingCard.test.tsx, …

    line 42

≈ “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-real-users.mdc
---
description: Hermes Mobile is a real-user product — never dogfood-only assumptions in tests or UX
globs:
  - hermes-mobile/**
alwaysApply: false
---

# Hermes Mobile — real users product

**User directive (permanent):** Hermes Mobile is a product for **real users**, not Igor-only USB dogfood.

## Brand-new user mindset (every test)

**Always treat every test as if it is a brand new user.**

Before claiming fixed, shipped, or "works on device", assume the tester has:

- Never paired before; no saved gateway profiles; no dev backdoor unlocked
- No `adb` cable; may be on **cellular** or home Wi‑Fi only
- Installed from **release APK / Play** — not Metro, not debug dev-client
- No knowledge of Mac hostname, tunnel URLs, or relay codes
- First launch: empty recents, honest disconnected copy, onboarding must work

Do **not** pass tests that only work because Igor's Mac is plugged in, `adb reverse` is set, or `developerLeashUnlock` is on.

## Product bar

- Onboarding: QR/deep link / Find computers — not "paste 127.0.0.1" without context
- Leash Pro / ThumbGate API for subscribers — dev backdoor is Igor-only, not the user path
- Cellular + multi-Mac: tunnel wizard copy must be actionable
- Maestro E2E on release build where possible; unit tests must not assume Igor fixtures as "default user"

See `hermes-mobile/docs/REAL-USER-READINESS.md` when present.

## Fresh-user test contract

1. **Cold start (no profiles):** `ConnectMacGate` shows `fresh-user-onboarding-card` with steps 1–4 and primary CTA **Find computers** (`connect-search-wifi`).
2. **Silent heal:** Returning users with a saved Mac get ~30s auto-heal (`CONNECTION_HEAL_EXHAUSTED_AFTER=6` × 5s) before `ChatConnectionPanel` + numbered steps; status pills hidden during heal.
3. **One CTA:** Exactly one primary button in connection UI (Find computers / Fix USB connection / Add [Mac] via Tailscale chip — not three competing banners).
4. **Tailscale on cellular:** `TailscaleDiscoveryBanner` with **Add Igors-Mac-mini** (or discovered hostname) appears in **Choose your Mac** modal and connection panel — not Settings-only.
5. **Jargon ban in primary onboarding:** No "gateway", "LAN", "Pair relay" in `ConnectMacGate`, `FreshUserOnboardingCard`, or `ChatConnectionPanel` hero copy.
6. **Tests:** Run `npm run test:ci`; onboarding copy guarded by `freshUserOnboarding.test.ts`, `FreshUserOnboardingCard.test.tsx`, `ChatConnectionPanel.test.tsx`.

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.