All authors
Claude Skills by ThiagoFdaSLopes
github.com/ThiagoFdaSLopes7 skills0 installs1 views
- Game DebugFind the root cause of a gameplay bug, crash, regression, desync or odd behaviour and apply the smallest correct fix with regression coverage. Use when the user reports a bug, pastes a log, stack trace or repro steps, or asks "why does X happen". Never fabricates a root cause - labels hypotheses when reproduction is impossible.Votes: 0GitHub stars: 2
- Game Dev QuestlineEntry point for the game-dev suite. Use when a request is about a game (design, mechanics, Unity/Godot/Unreal/custom engines, gameplay bugs, FPS/memory, game code review) and it is not obvious which specialised skill applies. Routes to game-plan, game-implement, game-debug, game-review, game-test or game-optimize.Votes: 0GitHub stars: 2
- Game ImplementImplement a game feature, system or change from a blueprint, ticket, spec or plain request - pick the test seams, build it test-first in vertical slices, run the checks as you go, review the diff, and hand it off committed or ready to commit. Use when the user asks to implement, add, build, wire up, change or refactor gameplay, systems, UI, tooling or engine code (Unity, Godot, Unreal, custom), or says "implement the blueprint / ticket #N". Asks only at forks that block correctness or touch a...Votes: 0GitHub stars: 2
- Game OptimizeDiagnose and fix FPS drops, stutter, memory growth, long loads, input latency or scaling problems by measuring first, changing one bottleneck at a time, and comparing before/after under the same conditions. Use when the user mentions performance, frame rate, hitching, memory, load time, GC spikes, draw calls or latency. Without measurements it proposes an instrumented experiment instead of promising gains.Votes: 0GitHub stars: 2
- Game PlanPlan a game or a game feature through dependency-ordered decisions - player promise, core loop, systems, architecture, production scope, risks - and end with a blueprint. Use for new games, new features, vague requirements, "X or Y" design choices, scope decisions, and when the user asks to plan, compare or decide before building. Planning-only - does not change code.Votes: 0GitHub stars: 2
- Game ReviewReview game code, a PR/diff, a system design or an architecture for bugs, unsafe assumptions, regressions, coupling and test gaps, ranked by severity with file locations. Use when the user says review, audit, "look over", "is this ok", or shares a PR. Read-only - never edits unless explicitly asked.Votes: 0GitHub stars: 2
- Game TestVerify game behaviour - choose and write unit, integration, play-mode or manual/playtest checks for a feature, run what the environment allows, and report observed vs unverified results. Use when the user asks to test, add tests, verify, check a milestone's completion criteria, or write a playtest plan. Performance baselines belong to game-optimize.Votes: 0GitHub stars: 2