From magic-powers
Use when diagnosing slow code, optimizing queries, reducing latency, or profiling application performance
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
Measure first, optimize second. Never optimize without profiling data — intuition about bottlenecks is wrong ~90% of the time.
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.
Measure first, optimize second. Never optimize without profiling data — intuition about bottlenecks is wrong ~90% of the time.
Core principle: Profile → Identify bottleneck → Fix → Measure improvement → Repeat.
1. Define target metric (e.g., p95 < 200ms)
2. Profile to find actual bottleneck
3. Fix the #1 bottleneck only
4. Measure — did it improve?
5. Repeat until target met
| Pattern | Problem |
|---|---|
| Premature optimization | Wasting time on non-bottlenecks |
| Optimizing without measuring | No proof it helped |
| Micro-optimizing | Loop tricks save nanoseconds, architecture saves seconds |
| Caching everything | Cache invalidation bugs, stale data |