Skip to content

notque/vexjoy-agent / skills/game/game-dev

game-dev

Flagged

Game development: design, asset pipelines, Phaser, Unity CLI and builds, vanilla JS frontend, GM mode, match booking.

FileKindSize
SKILL.mdskill md14.7 KB
references/anchor-alignment.mdmarkdown16.0 KB
references/animate-scaffolds.mdmarkdown2.0 KB
references/arcade-physics.mdmarkdown7.4 KB
references/artifacts-and-prototyping.mdmarkdown1.5 KB
references/asset-sources.mdmarkdown7.9 KB
references/audit-and-red-team.mdmarkdown795 B
references/autonomous-improvement.mdmarkdown10.3 KB
references/backend-chain.mdmarkdown10.4 KB
references/bg-removal-local.mdmarkdown22.7 KB
references/build-scaffolds.mdmarkdown2.0 KB
references/capabilities/01-design-red-team-audit.mdmarkdown3.9 KB
references/capabilities/02-emotional-canvas-moodboard.mdmarkdown3.7 KB
references/capabilities/03-game-design-attribution-audit.mdmarkdown3.6 KB
references/capabilities/04-game-design-bartle-archetype-audit.mdmarkdown3.7 KB
references/capabilities/05-game-design-big-five-personality-audit.mdmarkdown3.6 KB
references/capabilities/06-game-design-brainstorm-methods.mdmarkdown3.9 KB
references/capabilities/07-game-design-core-loop-extractor.mdmarkdown3.7 KB
references/capabilities/08-game-design-craft-critique.mdmarkdown3.5 KB
references/capabilities/09-game-design-creative-unblocker.mdmarkdown3.5 KB
references/capabilities/10-game-design-design-pillars-extractor.mdmarkdown3.5 KB
references/capabilities/11-game-design-emotional-canvas.mdmarkdown3.6 KB
references/capabilities/12-game-design-failure-loop-audit.mdmarkdown3.8 KB
references/capabilities/13-game-design-fairness-frustration-audit.mdmarkdown3.6 KB
references/capabilities/14-game-design-fantasy-extractor.mdmarkdown3.6 KB
references/capabilities/15-game-design-feature-prioritization.mdmarkdown3.6 KB
references/capabilities/16-game-design-five-options.mdmarkdown3.5 KB
references/capabilities/17-game-design-flow-audit.mdmarkdown3.6 KB
references/capabilities/18-game-design-fogg-behavior-audit.mdmarkdown3.6 KB
references/capabilities/19-game-design-friction-journey-audit.mdmarkdown3.8 KB
references/capabilities/20-game-design-ftue-hero-journey-audit.mdmarkdown3.7 KB
references/capabilities/21-game-design-goal-density-and-immediacy-audit.mdmarkdown3.5 KB
references/capabilities/22-game-design-goal-framing.mdmarkdown3.5 KB
references/capabilities/23-game-design-granular-player-motivation-audit.mdmarkdown4.0 KB
references/capabilities/24-game-design-grow-design.mdmarkdown3.5 KB
references/capabilities/25-game-design-ideal-outcome-backcasting.mdmarkdown3.4 KB
references/capabilities/26-game-design-kpi-coverage-audit.mdmarkdown3.8 KB
references/capabilities/27-game-design-leaderboard-audit.mdmarkdown3.9 KB
references/capabilities/28-game-design-leaderboard-builder.mdmarkdown3.8 KB
references/capabilities/29-game-design-molyneux-lens.mdmarkdown3.5 KB
references/capabilities/30-game-design-multiplayer-feature-audit.mdmarkdown3.8 KB
references/capabilities/31-game-design-novelty-spectrum-audit.mdmarkdown3.6 KB
references/capabilities/32-game-design-one-page-design-doc.mdmarkdown3.8 KB
references/capabilities/33-game-design-one-thing-to-remove.mdmarkdown3.6 KB
references/capabilities/34-game-design-option-generation.mdmarkdown3.5 KB
references/capabilities/35-game-design-peak-end-audit.mdmarkdown3.6 KB
references/capabilities/36-game-design-perceived-randomness-audit.mdmarkdown3.7 KB
references/capabilities/37-game-design-pitch-deck-audit.mdmarkdown3.8 KB
references/capabilities/38-game-design-player-motivation-audit.mdmarkdown3.5 KB
references/capabilities/39-game-design-player-need-satisfaction-audit.mdmarkdown3.6 KB
references/capabilities/40-game-design-player-persona-extractor.mdmarkdown4.2 KB
references/capabilities/41-game-design-player-perspective-reframe.mdmarkdown3.7 KB
references/capabilities/42-game-design-player-segment-perception-audit.mdmarkdown3.6 KB
references/capabilities/43-game-design-player-values-mapper.mdmarkdown3.8 KB
references/capabilities/44-game-design-premium-pass-audit.mdmarkdown3.8 KB
references/capabilities/45-game-design-prosocial-session-chapters.mdmarkdown3.7 KB
references/capabilities/46-game-design-prototype-intent-audit.mdmarkdown3.7 KB
references/capabilities/47-game-design-prototyping-companion.mdmarkdown3.6 KB
references/capabilities/48-game-design-roadblock-reframing.mdmarkdown3.5 KB
references/capabilities/49-game-design-smart-goal-audit.mdmarkdown3.6 KB
references/capabilities/50-game-design-social-satisfaction-matrix.mdmarkdown3.7 KB
references/capabilities/51-game-design-systematizing-empathizing-audit.mdmarkdown3.6 KB
references/capabilities/52-game-design-thinking-fast-and-slow-audit.mdmarkdown3.6 KB
references/capabilities/53-game-design-transformative-reuse.mdmarkdown3.6 KB
references/capabilities/54-game-design-unknown-unknowns-prototyping.mdmarkdown3.6 KB
references/capabilities/55-game-design-zeigarnik-effect-audit.mdmarkdown3.6 KB
references/capabilities/56-game-dev-budget-estimator.mdmarkdown3.8 KB
references/capabilities/57-game-dev-first-steps.mdmarkdown3.6 KB
references/capabilities/58-game-dev-team-gap.mdmarkdown3.6 KB
references/capabilities/59-game-dev-time-estimator.mdmarkdown3.8 KB
references/capabilities/60-moodboard-generator.mdmarkdown4.0 KB
references/capabilities/61-software-team-conflict-patterns.mdmarkdown3.8 KB
references/capability-catalog.mdmarkdown18.4 KB
references/capability-map.mdmarkdown1.7 KB
references/capability-matrix.mdmarkdown12.5 KB
references/capacitor-ios.mdmarkdown7.3 KB
references/cognition-and-choice.mdmarkdown1.2 KB
references/cognitive-and-behavioral-lenses.mdmarkdown1.2 KB
references/combat-effects-upgrade.mdmarkdown13.3 KB
references/combat-effects-upgrade/css-3d-card-transforms.mdmarkdown10.1 KB
references/combat-effects-upgrade/css-particle-migration.mdmarkdown13.3 KB
references/combat-effects-upgrade/framer-motion-combat-juice.mdmarkdown11.9 KB
references/concept-and-loop.mdmarkdown1.5 KB
references/core-loop-and-pillars.mdmarkdown835 B
references/core-patterns.mdmarkdown8.2 KB
references/cpu-systems-harmony.mdmarkdown3.4 KB
references/creative-and-options.mdmarkdown2.0 KB
references/creative-direction.mdmarkdown1.3 KB
references/deploy.mdmarkdown5.3 KB
references/design-artifacts.mdmarkdown1.0 KB
references/emotion-and-presentation.mdmarkdown1.1 KB
references/error-catalog.mdmarkdown22.6 KB
references/fairness-and-failure.mdmarkdown1.2 KB
references/fairness-and-learning.mdmarkdown1.3 KB
references/fal-ai-image.mdmarkdown7.1 KB
references/frame-detection.mdmarkdown20.0 KB
references/full-diagnostic.mdmarkdown4.2 KB
references/game-asset-generator.mdmarkdown9.5 KB
references/game-audio.mdmarkdown7.5 KB
references/game-feel-patterns.mdmarkdown12.2 KB
references/game-pipeline.mdmarkdown11.5 KB
references/game-qa.mdmarkdown6.7 KB
references/game-sprite-pipeline.mdmarkdown33.4 KB
references/gm-brilliant-implementation.mdmarkdown13.4 KB
references/grid-shapes.mdmarkdown8.0 KB
references/meshyai.mdmarkdown7.3 KB
references/motion-pipeline.mdmarkdown7.6 KB
references/output-formats.mdmarkdown9.4 KB
references/pacing-and-return.mdmarkdown1.6 KB
references/performance.mdmarkdown7.8 KB
references/phaser-gamedev.mdmarkdown7.5 KB
references/pipeline-spec.jsonconfig23.5 KB
references/pixel-art-sprites.mdmarkdown8.7 KB
references/pixijs-combat-renderer.mdmarkdown12.1 KB
references/pixijs-combat-renderer/combat-visual-effects.mdmarkdown7.8 KB
references/pixijs-combat-renderer/pixi-2d-lighting.mdmarkdown6.6 KB
references/pixijs-combat-renderer/pixi-particle-systems.mdmarkdown9.2 KB
references/pixijs-combat-renderer/pixi-performance.mdmarkdown4.8 KB
references/pixijs-combat-renderer/pixi-post-processing.mdmarkdown6.3 KB
references/pixijs-combat-renderer/pixi-react-integration.mdmarkdown5.2 KB
references/planning-and-communication.mdmarkdown1.6 KB
references/planning-and-production.mdmarkdown1.8 KB
references/player-and-social.mdmarkdown2.3 KB
references/polish-scaffolds.mdmarkdown1.9 KB
references/progression-and-economy.mdmarkdown1.0 KB
references/promo-video.mdmarkdown6.6 KB
references/prompt-rules.mdmarkdown15.2 KB
references/quality-gates.mdmarkdown6.4 KB
references/rive-skeletal-animator.mdmarkdown7.6 KB
references/rive-skeletal-animator/rive-animation-library.mdmarkdown8.1 KB
references/rive-skeletal-animator/rive-async-patterns.mdmarkdown5.6 KB
references/rive-skeletal-animator/rive-character-pipeline.mdmarkdown5.6 KB
references/rive-skeletal-animator/rive-performance.mdmarkdown5.4 KB
references/rive-skeletal-animator/rive-react-setup.mdmarkdown9.9 KB
references/rive-skeletal-animator/rive-vs-spine-decision.mdmarkdown6.0 KB
references/road-to-aew-integration.mdmarkdown7.8 KB
references/social-and-competitive-design.mdmarkdown1.1 KB
references/social-and-competitive.mdmarkdown1.5 KB
references/spritesheets.mdmarkdown6.2 KB
references/stage-contracts.mdmarkdown11.1 KB
references/style-presets.mdmarkdown5.1 KB
references/subagent-delegation.mdmarkdown2.2 KB
references/tilemaps-and-physics.mdmarkdown13.6 KB
references/tilemaps.mdmarkdown7.0 KB
references/unity-batchmode-builds.mdmarkdown9.2 KB
references/unity-cli.mdmarkdown10.9 KB
references/unity-licensing.mdmarkdown5.0 KB
references/vfx-containment.mdmarkdown3.1 KB
references/workflow-dag.mdmarkdown4.1 KB
references/worldlabs.mdmarkdown7.9 KB
references/wrestler-archetypes.mdmarkdown7.2 KB
scripts/deterministic_idle.pyscript7.8 KB
scripts/fal_queue_image_run.pyscript9.4 KB
scripts/imgdiff.pyscript5.0 KB
scripts/meshy-generate.mjsscript11.1 KB
scripts/optimize-glb.mjsscript3.8 KB
scripts/portrait_pipeline.pyscript31.2 KB
scripts/qa_artifacts.pyscript14.4 KB
scripts/road_to_aew_integration.pyscript6.6 KB
scripts/row_job_status.pyscript8.6 KB
scripts/sprite_anchor.pyscript30.1 KB
scripts/sprite_assemble.pyscript16.0 KB
scripts/sprite_bg.pyscript28.5 KB
scripts/sprite_canvas.pyscript11.9 KB
scripts/sprite_generate.pyscript13.9 KB
scripts/sprite_pipeline.pyscript54.9 KB
scripts/sprite_process.pyscript13.5 KB
scripts/sprite_prompt.pyscript41.8 KB
scripts/sprite_slicing.pyscript38.7 KB
scripts/sprite_verify.pyscript58.5 KB
scripts/test_content_aware_extraction.pyscript13.4 KB
scripts/test_no_status_laundering.pyscript6.9 KB
scripts/test_phases_4_5_7_8.pyscript16.4 KB
scripts/test_pipeline_glue.pyscript20.9 KB
scripts/test_pipeline_patterns.pyscript10.9 KB
scripts/test_rc3_frames_distinct_threshold.pyscript14.2 KB
scripts/test_rc4_mass_centroid_default.pyscript8.3 KB
scripts/test_rc5_despill_pre_upscale.pyscript7.9 KB
scripts/test_slice_grid_cells.pyscript6.4 KB
scripts/test_slicer_strict_pitch_default.pyscript11.6 KB
scripts/test_verifier_cell_parity.pyscript9.0 KB
scripts/test_verify_gates.pyscript23.2 KB
scripts/tests/test_fal_queue_image_run.pyscript908 B
scripts/video_extract_frames.pyscript4.3 KB
scripts/video_process_frames.pyscript7.6 KB
scripts/video_select_frames.pyscript6.4 KB
scripts/with_server.pyscript5.8 KB

references/autonomous-improvement.md

View on GitHub
# Autonomous game improvement

Use this protocol whenever the user asks to improve a game, retention, churn, engagement, return rate, player experience, or a product with game-like loops. Its job is to find and act on meaningful player improvements without waiting for a narrowly specified feature.

## Operating contract

1. Begin with the target repository's governing instructions and applicable local game, product, UI, implementation, analytics, research, and testing skills.
2. Treat the playable product and its evidence as the source of truth. A feature request, KPI target, or framework can generate hypotheses; it cannot override observed player harm.
3. Run greedily. For an isolated player moment, load every neighboring domain that could alter the diagnosis. For retention, churn, or whole-product improvement, run all 61 capability packets and record a disposition for each.
4. Move from evidence to action. Implement a small reversible improvement when it is within repository authority, technically safe, and the player benefit is clear enough to test. Otherwise create an implementation-ready task with the exact decision that needs authority.
5. Optimize for voluntary return, understanding, agency, competence, belonging, fairness, and trust. Never use hidden costs, forced notifications, punitive absence, shame, manipulative scarcity, confusing probability, or social pressure as an improvement.

## Improvement cycle

### 1. Build the evidence map

Inventory the game promise, target players, current build and entry points, rules, state, UI copy, reward schedules, progression, social systems, failures, return surfaces, telemetry definitions, tests, player research, support, reviews, analytics, backlog, and recent changes. Mark every conclusion as observed, documented, measured, or inferred.

For retention or engagement, trace at least these paths:

- arrival → first intention → first meaningful action → feedback → next choice;
- recurring session → goal selection → effort → reward or failure → closing moment → voluntary reason to return;
- lapsed player → re-entry cue → comprehension → catch-up → value or exit;
- where relevant, invitation → cooperation or competition → recognition → conflict/abuse recovery.

### 2. Run the design sweep

Load the capability matrix and all implicated cards. A systemic request must sweep the whole matrix, including motivation, needs, persona, friction, goal density, flow, failure/fairness, randomness, progression, social comparison, premium systems, emotion, instrumentation, prototyping, production scope, and red-team critique.

For each candidate issue, write a compact finding with: evidence, player moment and segment, lost need or expectation, competing causes, severity, confidence, affected system/files, smallest viable change, accessibility/trust risk, owner, and test.

Use motivation frameworks as hypotheses rather than diagnoses. In particular, distinguish:

| Signal | Product question | Safe design direction |
|---|---|---|
| Autonomy loss | Does the player meaningfully choose a goal, route, pace, or stop point? | Add understandable choices and graceful exits; remove forced steps. |
| Competence loss | Can the player predict, practice, recover, and see improvement? | Improve feedback, goal clarity, retry learning, and fair catch-up. |
| Relatedness loss | Does social play create belonging rather than exposure or comparison harm? | Support cooperative contribution, recognition, boundaries, and recovery. |
| Extrinsic overshadowing | Are rewards replacing the value of the activity itself? | Strengthen the core activity and vary meaningful challenges before adding rewards. |
| Amotivation/friction | Does effort lack context, agency, or visible progress? | Remove dead steps, explain value at the decision point, or create a smaller meaningful goal. |

### 3. Publish the complete improvement queue

Prioritize findings by player harm or value, confidence, reach, reversibility, cost, learning value, dependency risk, accessibility, and trust. Do not collapse these into a single score without preserving the trade-offs.

Classify each recommendation:

| Class | Action |
|---|---|
| Safe and reversible | Implement on a scoped branch, add or update tests, and document the player hypothesis. Examples: clearer goal/reward copy, a recoverable retry state, a misleading cue correction, an accessible setting default, a removed dead-end, or instrumentation that measures player understanding. |
| Needs a product choice | Give two to five materially different options with player, delivery, and validation consequences; identify the owner and decision deadline. |
| Irreversible, paid, social-risk, or live-operations change | Do not enact automatically. Supply an implementation-ready proposal, abuse/trust review, rollback plan, and explicit authority needed. |
| Evidence gap | Create the smallest observation, playtest, prototype, or instrumentation task that can distinguish the leading explanations. |

For every implementation, trace the repository's local code and test conventions; use the relevant implementation skill rather than inventing a parallel architecture. Keep the change scoped to the discovered player problem. Re-run the applicable tests and preserve a clear rollback path.

The output is a detailed, exhaustive queue, not a short set of representative ideas. Give every actionable finding an ID and include: player moment and affected segment, evidence and confidence, severity, root-cause and competing hypotheses, exact files/systems likely affected, player-visible change, implementation steps, dependencies, owner skill or role, tests, benefit measure, harm guard, rollback, and disposition. Group the queue into:

- **Fix now** — safe, reversible, evidence-supported changes that can be implemented in the repository.
- **Fix next** — actions with known dependencies or a bounded prototype/instrumentation prerequisite.
- **Decision required** — materially different product, economy, social, paid, legal, or live-operations choices, each with options and a recommended decision.
- **Research required** — unresolved causes with the shortest discriminating observation, playtest, or data task.

### 4. Execute the fix queue with the wider skill system

Do not stop after reporting. Work through every `Fix now` item in priority order, then advance newly unblocked `Fix next` items. For each item, discover the target repository's local skills, agents, and governing instructions, then route to all capabilities that materially improve the outcome. Typical collaborators are the repository's game or engine implementation guidance for rules and state, UI/design guidance for player-facing flows, analytics/data guidance for instrumentation, research guidance for evidence gaps, and testing/quality guidance for verification. In this toolkit, inspect the installed skill index rather than assuming a fixed set; the target game repository's own skills take precedence where they are more specific.

For each queued item:

1. Create a scoped implementation task from the finding and load the selected companion guidance.
2. Make the change, add or update the narrowest meaningful test or reproducible check, and run the repository's relevant quality gate.
3. Re-inspect the player path affected by the change; confirm that it improves the stated moment without moving harm elsewhere.
4. Record the change, evidence, files, test result, benefit measure, harm guard, rollback, and next review date in the queue.
5. Continue to the next actionable item. Do not quietly replace unfixed items with a generic future backlog.

If an item needs authority, live access, a paid-system decision, a broad migration, or an irreversible social effect, prepare it to the same implementation depth and continue with all other safe items. It is a visible blocked item, not permission to end the improvement cycle.

### 5. Measure player benefit, not only movement

Before releasing a change, define:

- the affected player segment, moment, and expected behavioral change;
- a player-benefit signal (understanding, successful self-chosen completion, fair recovery, satisfaction, or observed value);
- a harm guard (confusion, abandonment after prompt, spend pressure, accessibility regression, social abuse, negative sentiment, or support burden);
- the comparison, sample/window, owner, decision date, and stop or rollback rule.

Interpret retention carefully: a longer session, more clicks, more spending, or fewer exits is not evidence of value by itself. Pair the business signal with a player-outcome measure and qualitative evidence.

To drive one of these signals to a stated target instead of stopping when the
queue empties, run the optimization loop. Call the Skill tool with `workflow` and run its Hill Climb mode.
It adds a measured baseline, accept/revert per change, and a plateau stop
(`skills/process/workflow/references/hc-domain-playbooks.md`).

### 6. Report and continue

Return the evidence ledger, 61-card coverage ledger when applicable, prioritized improvement backlog, exact changes made, tests run, measurement plan, unresolved decisions, and a next-cycle trigger. A valid improvement report says both what changed and what evidence would make the team reverse or extend it.

## Retention safety checks

Before proposing a retention change, explicitly test for these traps:

- Adding a reward loop when the core action lacks clarity, agency, or felt progress.
- Treating notifications, streak loss, timer pressure, or currency scarcity as a replacement for a player-chosen reason to return.
- Adding leaderboards where comparison will disproportionately demoralize, expose, or exclude players.
- Increasing task volume or grind rather than improving choice, learning, or payoff.
- Reading aggregate retention as proof when new, returning, accessibility-constrained, and dissatisfied segments have different experiences.

If a trap is present, the repair belongs earlier in the player path. State that plainly and prioritize the underlying experience over a superficial engagement lever.

## Completion gate

Do not conclude with a generic backlog. The cycle is complete only when it has inspected the actual repository, routed all material design and implementation guidance, made or specified the next smallest evidence-supported improvement, verified its technical path, and established both benefit and harm measures for the next decision.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall