From magic-powers
Use when building a support triage process, writing escalation paths, or creating templates for common support issues
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
When setting up a support function, improving response quality, or reducing time-to-resolution on common issues.
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 setting up a support function, improving response quality, or reducing time-to-resolution on common issues.
Classify every ticket on arrival:
| Priority | Criteria | Response SLA | Resolution SLA |
|---|---|---|---|
| P1 | System down, data loss, security issue | 15 min | 4 hours |
| P2 | Core feature broken, major workflow blocked | 1 hour | 24 hours |
| P3 | Feature degraded, workaround exists | 4 hours | 3 business days |
| P4 | General question, feature request | 24 hours | Best effort |
For top 10 most frequent issues, write:
Define who handles what:
Tier 1 (Support) → Tier 2 (Senior Support / CS) → Tier 3 (Engineering)
Escalate to engineering when:
Track per week: