Frontend Observability Engineer
Frontend monitoring covering session replay, error budgets, Core Web Vitals, real user monitoring, synthetic testing, and performance debugging for web applications.
SupaScore
84.25Best for
- ▸Debugging Core Web Vitals failures with session replay analysis to identify specific user interactions causing poor LCP, INP, or CLS scores
- ▸Implementing error budget tracking for frontend releases with automated rollback when error rates exceed SLO thresholds
- ▸Setting up RUM monitoring pipeline to capture field performance data across different user segments and geographic regions
- ▸Configuring synthetic monitoring with Playwright to catch performance regressions before they reach production users
- ▸Building observability dashboards that correlate business metrics with frontend performance to drive engineering priorities
What you'll get
- ●Detailed monitoring configuration with specific Core Web Vitals thresholds (LCP <2.5s for 75th percentile), error budget calculations (99.5% availability = 21.6 minutes downtime/month), and attribution setup for debugging poor scores
- ●Step-by-step session replay analysis workflow identifying rage clicks, dead clicks, and performance bottlenecks with specific code-level recommendations for optimization
- ●Comprehensive dashboard design mockup showing performance distribution across user segments, error trend analysis, and automated alerting rules tied to business impact metrics
Not designed for ↓
- ×Backend API monitoring or database performance optimization
- ×Mobile app performance monitoring (native iOS/Android applications)
- ×Network infrastructure monitoring or CDN configuration
- ×Server-side error tracking or application security monitoring
Web application URLs, existing monitoring tool access, performance requirements (SLOs), and current tech stack details including frontend frameworks and deployment pipeline.
Actionable performance monitoring setup with specific metric thresholds, alerting configurations, dashboard designs, and debugging playbooks for common performance issues.
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 6 sources (4 official docs, 1 books, 1 web)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
Initial version
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
Performance-Driven Release Pipeline
Monitor performance baselines, optimize Core Web Vitals, then implement performance-gated deployments with automated rollback on regression
Activate this skill in Claude Code
Sign up for free to access the full system prompt via REST API or MCP.
Start Free to Activate This Skill© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice