From magic-powers
Use when defining definition of done, setting release criteria, or building automated quality checks into the CI/CD pipeline
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
When establishing what "done" means, preventing low-quality code from reaching production, or reducing manual QA overhead.
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 establishing what "done" means, preventing low-quality code from reaching production, or reducing manual QA overhead.
Agree team-wide: a story is done only when ALL of these pass:
DoD applies to every story — no exceptions without explicit team agreement.
Pipeline structure:
PR opened → lint → unit tests → build
→ integration tests
→ security scan (Snyk/Semgrep)
→ coverage check (must not drop below threshold)
→ [merge gated on all passing]
Merge to main → E2E tests → staging deploy → smoke tests
→ [production deploy gated on all passing]
Before any production release:
Some gates should block unconditionally:
Make these non-negotiable and enforce in CI — not as optional warnings.