incident-response

Name: incident-response
Rating: 5 (1 reviews)
Author: LukeJMadden

Design e Frontend

Author: LukeJMadden

5-step incident response playbook. Use when a service is down, degraded, or experiencing errors.

1stars

Updated 2 months ago

View on GitHub ↗License: MIT

How to add

/plugin marketplace add LukeJMadden/Veltrix-skills

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/incident-response-lukejmadden/svg)](https://www.skillteca.com.br/skills/incident-response-lukejmadden?utm_source=badge&utm_medium=readme&utm_campaign=badge)

#ai

Related skills

See all in Design e Frontend →

webapp-testing

143.8k

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Design e Frontend#testby anthropics

brand-guidelines

143.8k

Applies Anthropic's official brand colors and typography to any artifact that may benefit from its look-and-feel. Use it when brand colors, style guidelines, visual formatting, or company design standards apply.

Design e Frontendby anthropics

frontend-design

143.8k

Creates distinctive, production-grade frontend interfaces with high design quality, generating creative, polished code and UI design that avoids generic AI aesthetics. Use for building web components, pages, and applications, or for styling/beautifying web UIs.

Design e Frontend#css#aiby anthropics

web-artifacts-builder

143.8k

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

Design e Frontend#css#aiby anthropics

Category alert

Get new Design e Frontend skills every Monday

One short email with only the new Design e Frontend skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

Follow this playbook for every incident. No shortcuts.

The 5 Steps

1. CONTAIN (first 5 minutes)

Stop the bleeding. Prevent further damage.

Can we rollback to the last working version?
Can we disable the broken feature without taking down everything?
Is customer data at risk?
Who needs to be notified right now?

2. DIAGNOSE (next 15 minutes)

Find the root cause using data, not guesses.

Check logs: what changed? when did errors start?
Check deployments: was there a recent

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.