All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Game Procedural World Placement ValidationUse when a task involves validating required gameplay objects in procedurally generated worlds to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live serv...Votes: 0GitHub stars: 2
- Game Programming LanguagesUse when a task involves choosing a programming language and runtime for a game prototype or production target to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run third-pa...Votes: 0GitHub stars: 2
- Game Progression Curve Sensitivity ReviewUse when a task involves reviewing how tuning changes affect player progression pace and resource needs to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change ...Votes: 0GitHub stars: 2
- Game Quest State Machine Consistency AuditUse when a task involves auditing quest states and transitions for impossible or stuck objectives to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live s...Votes: 0GitHub stars: 2
- Game Random Number Abuse Risk ReviewUse when a task involves reviewing whether random outcomes can be predicted or manipulated in a game system to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not cha...Votes: 0GitHub stars: 2
- Game Ranked Leaderboard Integrity MonitoringUse when a task involves designing an evidence-based review for suspicious ranked scores or match outcomes to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not chan...Votes: 0GitHub stars: 2
- Game Reconnect Command Idempotency ReviewUse when a task involves checking that reconnecting clients do not repeat gameplay commands or rewards to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change l...Votes: 0GitHub stars: 2
- Game Region Match Latency Assignment ReviewUse when a task involves reviewing how player latency and region choice influence multiplayer match assignment to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not ...Votes: 0GitHub stars: 2
- Game Rollback Netcode Determinism ReviewUse when a task involves checking the determinism and resimulation assumptions required by rollback networking to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not ...Votes: 0GitHub stars: 2
- Game Save Schema Migration ReviewUse when a task involves reviewing versioned save-data migrations between game releases to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live services, p...Votes: 0GitHub stars: 2
- Game Scene Transition Memory Watermark ReviewUse when a task involves checking peak memory during scene changes, reloads, and background preloading to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change l...Votes: 0GitHub stars: 2
- Game Server Authority Validation ReviewUse when a task involves reviewing which gameplay decisions must be validated by an authoritative multiplayer server to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. D...Votes: 0GitHub stars: 2
- Game Server Tick Overrun Capacity ReviewUse when a task involves reviewing whether a multiplayer server completes each simulation tick within budget to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not ch...Votes: 0GitHub stars: 2
- Game Session Reward Idempotency ReviewUse when a task involves checking that end-of-session rewards are granted at most once despite retries to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change l...Votes: 0GitHub stars: 2
- Game Shader Variant Cardinality AuditUse when a task involves auditing shader permutation growth caused by keywords, materials, and platform variants to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do no...Votes: 0GitHub stars: 2
- Game Shader Warmup Stutter ValidationUse when a task involves checking whether shader compilation or pipeline creation causes gameplay stalls to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change...Votes: 0GitHub stars: 2
- Game Simulation Catchup Overrun PolicyUse when a task involves reviewing fixed-step catch-up behavior when rendering falls behind simulation to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change l...Votes: 0GitHub stars: 2
- Game Skill Rating Calibration AuditUse when a task involves auditing whether a multiplayer rating reflects outcomes and uncertainty over time to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not chan...Votes: 0GitHub stars: 2
- Game Skinned Animation Cost AttributionUse when a task involves attributing CPU and GPU costs in skeletal animation for a game scene to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live servi...Votes: 0GitHub stars: 2
- Game Snapshot Reconciliation Coherence AuditUse when a task involves auditing how client snapshots are applied and interpolated against server state to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change...Votes: 0GitHub stars: 2
- Game Status Effect Stacking Precedence AuditUse when a task involves auditing how simultaneous status effects stack, refresh, replace, or expire to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change liv...Votes: 0GitHub stars: 2
- Game Texture Residency Memory BudgetUse when a task involves budgeting texture residency and streaming memory for a target platform to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live ser...Votes: 0GitHub stars: 2
- Game Tutorial Completion Funnel AnalysisUse when a task involves analyzing where players abandon or misunderstand a game tutorial to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change live services,...Votes: 0GitHub stars: 2
- Game Tutorial Control Legend Consistency AuditUse when a task involves checking that tutorial instructions and control glyphs match active bindings to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change li...Votes: 0GitHub stars: 2
- Game Virtual Economy Source Sink AuditUse when a task involves auditing currency creation, spending, transfers, and removal in a game economy to establish the game, engine and release version, platform, player or test cohort, controlling design or technical artifact, evidence, data sensitivity, and approval boundary before applying the method. Separate measured behavior from simulation and design intent, verify the result with reproducible tests, preserve provenance, and report uncertainty and compatibility limits. Do not change ...Votes: 0GitHub stars: 2
- Godot 4 Migration Capability Surface MapUse when the actual capability boundary of Godot project migration needs to be distinguished from assumptions. Produce a capability map for Godot project migration covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to project version identity, script and scene co...Votes: 0GitHub stars: 2
- Godot 4 Migration Change Impact AssessmentUse when a proposed Godot project migration version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Godot project migration with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to project version identity, script and scene ...Votes: 0GitHub stars: 2
- Godot 4 Migration Failure Triage RecordUse when a reproducible Godot project migration symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Godot project migration with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to project version identity, script and scene compatibility, asset references, and r...Votes: 0GitHub stars: 2
- Godot 4 Migration Input Output ContractUse when the accepted inputs or produced outputs for Godot project migration need a checkable boundary. Produce an input/output contract for Godot project migration with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to project version identity, script and scene compatibility, asset reference...Votes: 0GitHub stars: 2
- Godot 4 Migration Integration Parity TraceUse when Godot project migration exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Godot project migration showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to project version identity, script and scene compatibility, asset references, and rollback b...Votes: 0GitHub stars: 2
- Godot 4 Migration Performance EnvelopeUse when Godot project migration must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Godot project migration with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to project version identity, script and scene compatibility, asset...Votes: 0GitHub stars: 2
- Godot 4 Migration Permission Boundary ReviewUse when Godot project migration may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Godot project migration showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to project version identity, script and scene compatibi...Votes: 0GitHub stars: 2
- Godot 4 Migration Release Handoff RecordUse when a Godot project migration review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Godot project migration with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to project version identity, script and scene co...Votes: 0GitHub stars: 2
- Godot 4 Migration Reproducibility Fixture PlanUse when a Godot project migration result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Godot project migration defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to project version i...Votes: 0GitHub stars: 2
- Godot 4 Migration Version CompatibilityUse when a Godot project migration integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Godot project migration with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to project version identity, script and sce...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Capability Surface MapUse when the actual capability boundary of Godot GDScript workflows needs to be distinguished from assumptions. Produce a capability map for Godot GDScript workflows covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to signal and scene boundaries, state transiti...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Change Impact AssessmentUse when a proposed Godot GDScript workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Godot GDScript workflows with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to signal and scene boundaries, state transi...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Failure Triage RecordUse when a reproducible Godot GDScript workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Godot GDScript workflows with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to signal and scene boundaries, state transitions, resource lifetime, and testable...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Input Output ContractUse when the accepted inputs or produced outputs for Godot GDScript workflows need a checkable boundary. Produce an input/output contract for Godot GDScript workflows with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to signal and scene boundaries, state transitions, resource lifetime, and ...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Integration Parity TraceUse when Godot GDScript workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Godot GDScript workflows showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to signal and scene boundaries, state transitions, resource lifetime, and testable behavior...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Performance EnvelopeUse when Godot GDScript workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Godot GDScript workflows with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to signal and scene boundaries, state transitions, resource life...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Permission Boundary ReviewUse when Godot GDScript workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Godot GDScript workflows showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to signal and scene boundaries, state transitions, re...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Release Handoff RecordUse when a Godot GDScript workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Godot GDScript workflows with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to signal and scene boundaries, state transiti...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Reproducibility Fixture PlanUse when a Godot GDScript workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Godot GDScript workflows defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to signal and scen...Votes: 0GitHub stars: 2
- Godot Gdscript Patterns Version CompatibilityUse when a Godot GDScript workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Godot GDScript workflows with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to signal and scene boundaries, state tra...Votes: 0GitHub stars: 2
- 3d Renderer DevelopmentUse when designing, implementing, or debugging a software 3D renderer, whether the target is a CPU rasterizer, ray tracer, or a bounded graphics pipeline to define coordinate conventions and a minimal image-producing slice, then verify projection, clipping, depth, and shading with deterministic scenes. Trigger for renderer projects or changes to geometry-to-image behavior.Votes: 0GitHub stars: 2
- Ai Image GenerationUse when a task involves planning or generating an image asset from a brief while controlling rights, likeness, and output requirements to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do no...Votes: 0GitHub stars: 2
- Blender AnimationUse when a task involves creating or reviewing a Blender animation with controlled timing, camera, and render checks to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run th...Votes: 0GitHub stars: 2
- Blender McpUse when a task involves controlling a Blender instance through an explicitly configured MCP server for scene inspection or editing to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not in...Votes: 0GitHub stars: 2
- Blender ModelingUse when a task involves creating or revising Blender meshes and product models with explicit geometry and deliverable constraints to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not ins...Votes: 0GitHub stars: 2