Use when building game systems, implementing Unity/Unreal Engine features, or optimizing game performance.
Use when building a PlayCanvas game's on-screen interface such as ready, pause, and victory overlays, menus, and live indicators like…
Use when implementing game math — vectors, transforms, interpolation, curves, random number generation, and common geometric recipes
Designs engaging gameplay loops, economies, and progression systems, balancing challenge and reward for interactive experiences.
Select and operate Apple Game Porting Toolkit 3 or 4 for bringing an existing Windows game or engine to Apple platforms.
Use when structuring a PlayCanvas game's control flow — a small state machine such as ready, playing, paused, and over, pointer-lock…
Create comprehensive game test scenarios.
Guide GameplayKit simulation and gameplay-architecture work.
Use when writing GDScript — static typing, await/coroutines, lambdas, match patterns, export annotations, inner classes, and common idioms
SDK setup, Gradle integration, AndroidManifest configuration, and first connection to Meta glasses
SDK setup, Swift Package Manager integration, Info.plist configuration, and first connection to Meta glasses
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases…
Post a reply comment to a GitHub issue. Use when the user wants to respond to an issue, acknowledge a bug report, or share a fix reference…
End-to-end GitHub issue workflow — list issues, pick one, implement the fix, commit, push, and reply to the reporter.
Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting…
Git commit and pull request guidelines using conventional commits.
Create standardized git commits, amends, or squash-merges from current repo state using conventional-commit-style summaries with…
Enforces industry-standard Git practices, Conventional Commits, and automated pre-commit validation workflows.
Use this skill immediately when the user mentions merge conflicts that need to be resolved.
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code…
Detects git forge (GitHub/GitLab/Bitbucket) and maps CLI commands cross-platform.