Performance Monitoring
Skill Purpose: Instrument and monitor application performance with metrics, alerts, and trend analysis.
Core Skill Pattern
Objective: Detect performance regressions early and track user experience over time.
Universal Pattern:
- •Define key metrics (latency, error rate, throughput)
- •Instrument services and pages
- •Collect and store metrics
- •Set alert thresholds and dashboards
- •Review trends and regressions
Key Decisions (Project-Specific):
- •Monitoring tooling and data retention
- •Alert thresholds and escalation rules
- •Sampling rates for client metrics
Project-Specific Implementation Notes
Customize per project:
- •Include Core Web Vitals for web apps
- •Distinguish backend vs frontend metrics
Example Metrics
- •p50/p95 response time
- •error rate by endpoint
- •Core Web Vitals
- •bundle size trends
Best Practices
- •Alert on user-impacting regressions only
- •Use percentiles, not averages
- •Keep dashboards focused and actionable
- •Review performance weekly
- •Tie alerts to runbooks
Stop Conditions
STOP and escalate if:
- •No metrics are defined
- •Alerts are noisy or missing
- •Monitoring does not cover critical paths
Skill Version: 1.0.0