From magic-powers
Use when writing runbooks for on-call engineers, documenting incident response steps, or creating operational playbooks
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
When documenting how to respond to alerts, investigate incidents, or operate a system at 3am with no context.
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.
When documenting how to respond to alerts, investigate incidents, or operate a system at 3am with no context.
Every runbook should have:
# Alert: [Alert Name]
## Severity
[P1/P2/P3] — [impact if this fires]
## Symptoms
- What does the user experience?
- Which metrics are affected?
## Immediate Actions (first 5 minutes)
1. Acknowledge the alert
2. [Specific command to run first]
3. [Decision point: if X, go to section A; if Y, go to section B]
## Investigation Steps
1. Check [dashboard link] — look for [what to look for]
2. Run: `[exact command]`
3. Check logs: `[exact log query]`
## Common Causes and Fixes
### Cause: [specific cause]
Fix: [exact steps]
### Cause: [another cause]
Fix: [exact steps]
## Escalation
If not resolved in 30 minutes, escalate to: [person/team + how]
## Post-Incident
- Create incident ticket in [system]
- Run postmortem if P1/P2