From magic-powers
Use when writing a Game Design Document (GDD), defining core mechanics, or planning player loops
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
When starting a new game project, aligning team members on what to build, or documenting mechanics for implementation.
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 starting a new game project, aligning team members on what to build, or documenting mechanics for implementation.
The 3 layers:
Write it as actions, not features: "Player fights → defeats enemy → gains resources → upgrades → faces harder enemy → (repeat)" is good. "Combat system with progression mechanics" is bad.
Per mechanic:
MoSCoW for game design: