From magic-powers
Use when writing a blameless postmortem after an incident, identifying root causes, and building follow-up action items
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
After any P1/P2 incident, or any incident that surprised the team, caused user impact, or revealed a systemic gap.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
After any P1/P2 incident, or any incident that surprised the team, caused user impact, or revealed a systemic gap.
# Postmortem: [Incident Title]
**Date:** YYYY-MM-DD
**Severity:** P1/P2
**Duration:** [start] → [end] ([total hours])
**User Impact:** [what users experienced, how many affected]
**Author(s):** [names]
## Summary
[2–3 sentences: what happened, what caused it, how it was resolved]
## Timeline
| Time (UTC) | Event |
|------------|-------|
| 14:00 | Alert fires: error rate > 5% |
| 14:05 | On-call acknowledges |
| 14:22 | Root cause identified |
| 14:35 | Mitigation applied |
| 14:40 | Error rate returns to baseline |
| 15:00 | Incident resolved |
## Root Cause Analysis (5 Whys)
[Walk the 5 Whys from symptom to root cause]
## What Went Well
[What worked — don't skip this section]
## What Went Poorly
[Gaps, surprises, things that slowed resolution]
## Action Items
| Item | Owner | Due |
|------|-------|-----|
| [specific fix] | @person | YYYY-MM-DD |