guardian / rules
Cursor rule1 starsChanged 5 months agoMITView on GitHub
Guardian — production monitoring & debugging method. Apply when the user is dealing with a production issue (error, crash, outage, slow endpoint, memory leak, crashing pod) or pastes a stack trace, logs, a Sentry issue, or Datadog/Kubernetes/APM output.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- guardianSkill
The file
Files
--- description: Guardian — production monitoring & debugging method. Apply when the user is dealing with a production issue (error, crash, outage, slow endpoint, memory leak, crashing pod) or pastes a stack trace, logs, a Sentry issue, or Datadog/Kubernetes/APM output. alwaysApply: false --- # Guardian Apply the Guardian production-debugging method. The full method and dispatch table are in `AGENTS.md`; per-domain knowledge is in `references/`. Read `AGENTS.md` and the matching `references/<topic>.md` for the signal at hand. Core rule — evidence before hypothesis: gather the signal, reconstruct the timeline (earliest anomaly, not loudest error), localize the failure to a layer, correlate across signals on shared keys (time window, trace_id, release, host) when more than one is present, then state a root cause separated from the symptom, plus immediate mitigation, the real fix, and the exact signal that verifies it. If evidence is insufficient, say so and name what would unblock it — never guess confidently. Match the response to the size of the problem: a 3-line answer (real problem / fix / verify) for an unambiguous small bug; the full structure (what's happening, timeline, root cause, fix, "if I'm wrong") for a real incident. Dispatch: stack trace → references/stack-traces.md · logs → references/log-analysis.md · Sentry → references/sentry.md · latency → references/performance.md · Kubernetes → references/kubernetes.md · PostgreSQL → references/postgresql.md · distributed trace → references/opentelemetry.md · Datadog → references/datadog.md · several signals → references/cross-signal-correlation.md
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
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.