web-rum
Use when an "enable observability" card asks for rum on a frontend, or web.* signals are unbound - how the developer collects Core Web Vitals and page views (web-vitals to the app's own endpoint as log lines, or Sentry / PostHog), what each event must carry, and what stays out of it
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- web-rum
- source
- GoogleChrome/web-vitals (Apache-2.0), getsentry/sentry-javascript and PostHog docs (MIT), adapted
- category
- observability
- description
- Use when an "enable observability" card asks for rum on a frontend, or web.* signals are unbound - how the developer collects Core Web Vitals and page views (web-vitals to the app's own endpoint as log lines, or Sentry / PostHog), what each event must carry, and what stays out of it
03 SKILL.md 正文
Real-user monitoring for a web frontend
What the frontend's golden signals need: Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift (judged at the 75th percentile), page views, and front-end errors. Choose one path per app; never ship two RUM SDKs.
Path 1 — the app's own backend (no vendor)
- Add
web-vitalsand report every metric once per page view:onLCP(send); onINP(send); onCLS(send); onFCP(send); onTTFB(send);wheresendposts{name, value, rating, id, navigationType, page, release}withnavigator.sendBeacon('/api/rum', body)(falling back tofetch(..., {keepalive: true})). - Page views: one event per route change from the router (not per render).
- The backend's
/api/rumendpoint validates the body (knownname, a numbervalue, a bounded size), rate-limits by client, and writes one structured log line per event —event=web_vital name=LCP value=2310 rating=needs-improvement page=/checkout release=1.42.0— and answers 204. Those lines are what a logs data source (Loki, Elasticsearch, the cloud's logging) reads; theweb.*signals bind to them. - Front-end errors:
window.addEventListener('error' | 'unhandledrejection')posting the message, stack, page and release to the same endpoint asevent=frontend_error.
page is the route pattern (/orders/:id), never the raw URL: ids and query strings are personal data and explode the label count.
Path 2 — Sentry
@sentry/browser (or @sentry/react, @sentry/nextjs) with browserTracingIntegration(); release and environment set from the build, tracesSampleRate 0.1 in production. Web Vitals and errors come with it; a sentry data source reads its issues and release health.
Path 3 — PostHog
posthog-js with capture_pageview: 'history_change' for single-page apps and capture_performance for web vitals; the project key is public, the host is the team's PostHog instance.
Either way
- No personal data in any event: no email, name, token, form value or full URL.
- Sample when traffic is high (10% of sessions still gives a stable p75).
- The release version rides on every event, so a deploy-impact read can compare before and after.
Acceptance criteria: "Given a visitor loads /checkout in production, then an LCP event for page /checkout with this release's version is readable from <data source> within a minute"; "Given a page throws, then a frontend_error event with its stack is recorded."
04 同仓库更多 Skills
visual-craft
暂无简介
ux-copy
Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check
screen-mockup-html
Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task
performance-awareness
How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.
design-variants
Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision
design-system-authoring
Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns