agentleFS
Sign inStart free
sukirman1901sukirman1901/frontend-expert/skills/monitoring/SKILL.md

monitoring

Skill9 starsChanged 2 months agoMITView on GitHub

Frontend observability — Sentry error tracking, CWV/performance monitoring, analytics, OpenTelemetry, alerting. Use when adding error boundaries, tracking production bugs, measuring LCP/INP, wiring analytics, or ops asks about monitoring/observability for a web UI — not for visual design polish.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use authentication, database and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    authentication

    Wire this in whenever the app uses or connects to data — records, a database, entities, per-user data, row-level security — or when the user wants sign-in, accounts, login, or protected pages. Rayfin data is always accessed as an authenticated user, so **data implies auth**; only a static page over public data skips it. The starter ships as a no-auth "hello world" that previews with no backend, and the full Fabric auth scaffolding is already in the project — this skill wires it in: AuthProvider + bootstrapAuth in main.tsx, the route guard in App.tsx, the sign-in page, sign-out, and the env/deploy requirement. Triggers: auth, authentication, sign in, sign-in, login, log in, sign out, logout, account, user, identity, protect route, require login, gated page, data, database, records, per-user, row-level security, who is the current user, Fabric auth, Entra.

    Also in 3 projects that use this

  • mijunriSkill

    database

    数据库脚本与操作规范。脚本放在 db_scripts 目录，遵循查询优化、事务、安全等实践。

    Also in 3 projects that use this

  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 4 projects that use this

  • mrgoonieSkill

    devops

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

    Also in 3 projects that use this

  • AnthropicSkill

    documentation

    Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add/fix Sentry (or similar) + error boundaries

    line 18

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “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
SKILL.md

Monitoring

Overview

Ship UI with enough production signal: errors, performance, and product analytics — without boiling the ocean.

When to use

  • Add/fix Sentry (or similar) + error boundaries
  • Performance monitoring / CWV in production
  • Analytics events for key UI flows
  • Alerting on error spikes or CWV regressions

When to skip

  • Pure visual polish (polish / /polish)
  • Local-only prototypes with no deploy target

MUST (when adding observability)

SignalMinimum
ErrorsBoundary on app shell / critical routes + reporting; scrub PII
SecretsDSN / keys via env — never commit
Sample ratesSane defaults for traffic (don’t 100% trace huge apps blindly)
AnalyticsFew high-value events (signup, checkout, critical CTA) — not every click
AlertsError rate or CWV budget with a named owner

Lab Lighthouse ≠ production monitoring — use devtools for local audits; this skill for shipped signal.

Workflow

  1. Errors — boundary + reporting; scrub PII
  2. Performance — sample traces; watch LCP/INP/CLS on key routes
  3. Analytics — few high-value events, not every click
  4. Alert — error rate / CWV budgets that someone will actually see

Agent boundaries

  • May decide: Vendor (Sentry vs other), which 3–5 analytics events matter
  • Must not: Hardcode DSNs; log emails/tokens; add analytics spam on every hover

Checklist

  • Error boundary on app shell / critical routes
  • DSN/env via env vars — not hardcoded secrets in git
  • Sample rates sane for traffic
  • No PII in events by default
  • Alerts have an owner
  • Key product events listed (not clickstream noise)

Depth

Full guide: references/monitoring.md.
Related: performance for build-time CWV; devtools for lab audits.

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.

Check your setup, free