From magic-powers
Use when choosing between Cloud Run and Cloud Functions, designing serverless compute on GCP, configuring concurrency/scaling, or building event-driven architectures. Covers GCP Cloud Developer domain: Designing apps (~36%).
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
- Deciding between Cloud Run, Cloud Functions, and App Engine
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.
| Option | Best for | Billing |
|---|---|---|
| Cloud Run | Containerized apps, any language, HTTP/gRPC | Per request + CPU |
| Cloud Functions (2nd gen) | Cloud Run under the hood, longer timeout, concurrency | Per request + CPU |
| App Engine Standard | Specific runtimes (Python/Java/Go/Node), instant scaling | Per instance hour |
| App Engine Flexible | Custom runtimes, Docker, always-on | Per instance hour |
roles/run.invoker for Cloud Run, roles/cloudfunctions.invoker