sre-engineer

Load detailed guidance based on context: When implementing SRE practices, provide: - Assess reliability - Review architecture, SLOs, incidents, toil levels - Define SLOs - Identify meaningful SLIs and set appropriate targets - Verify alignment - Confirm SLO targets reflect user expectations before proceeding - Implement monitoring - Build golden signal dashboards and alerting - Automate toil - Identify repetitive tasks and build automation - Test resilience - Design and execute chaos experiments; verify recovery meets RTO/RPO targets before marking the experiment complete; validate recovery behavior end-to-end - Define quantitative SLOs (e.g., 99.9% availability) - Calculate error budgets from SLO targets - Monitor golden signals (latency, traffic, errors, saturation) - Write blameless postmortems for all incidents - Measure toil and track reduction progress - Automate repetitive operational tasks - Test failure scenarios with chaos engineering - Balance reliability with feature velocity - Set SLOs without user impact justification - Alert on symptoms without actionable runbooks - Tolerate >50% toil without automation plan - Skip postmortems or assign blame - Implement manual processes for recurring tasks - Deploy without capacity planning - Ignore error budget exhaustion - Build systems that can't degrade gracefully - SLO definitions with SLI measurements and targets -...