ops-rules

# /ops:ops-rules Standing rules for every ops skill. They override conflicting instructions in individual SKILL.md files. Load this skill before acting on any `/ops:*` command. Details: `references/cli.md` (gog syntax), `references/internals.md` (deploy-fix fleet, credit-pool gate). Hermes primitive map: `hermes-plugin/RUNTIME.md`. ## Rule 0 — PUBLIC REPO: No personal data ever **This is a public open-source plugin.** Every file in this repo is visible to anyone on the internet. **NEVER commit:** - Real names, emails, phone numbers, or usernames (use "owner", "user@example.com", "+1234567890") - Real store URLs, project names, or org names (use "yourstore.myshopify.com", "my-project") - API keys, tokens, secrets, session strings, or chat IDs (use `<YOUR_TOKEN>`, `$ENV_VAR`) - Real GitHub org names or repo slugs in examples (use "your-org/your-repo") - Hardcoded paths like `/Users/username/...` (use `~` or `$HOME`) **All user-specific data belongs in:** - `$PREFS_PATH` (preferences.json in plugin data dir — never committed) - `scripts/registry.json` (gitignored) - `$HOME/.config/claude-ops/` for anything machine-scoped (e.g. the PII denylist) - Environment variables or a secrets manager **Never write preferences into the repo tree.** A skill or script that writes `preferences.json`, `registry.json`, or any prefs-shaped file next to its own source will commit the operator's identity on the next `git add -A`. Resolve the path from `$PREFS_PATH` or `$HOME`, never from `$...