agentleFS
jammyfujammyfu/open-game-skills/skills/engines/pixijs/SKILL.md

pixijs

Skill13 starsChanged 24 days agoMITView on GitHub

Use when an existing PixiJS game needs skill contracts mapped onto its Ticker, scene graph, input, animation, collision graph, or a project-owned logical simulation loop.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the project already has a logical accumulator, preserve its configured rate.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PixiJS adapter

Inspect the PixiJS version and whether the application uses a shared, private, manual, or custom Ticker before changing timing ownership.

Timing

PixiJS Ticker callbacks are frame-driven and normally run once per animation frame. deltaTime/deltaMS, min/max FPS controls and clamping do not by themselves create deterministic fixed-step gameplay.

If the project already has a logical accumulator, preserve its configured rate. Add a fixed accumulator only when the game's discipline contract requires it; do not declare 60 Hz as an engine requirement. Rendering and interpolation may remain on Ticker cadence.

Hitstop freezes only the selected actor/action/animation clock. Never use ticker.stop() as per-actor hitstop because it pauses unrelated listeners/rendering.

Lifecycle and resources

The engine-neutral rules live in audio-feel, juice-vfx, asset-runtime, performance-budget and soak-stability; this section only maps them onto PixiJS.

  • audio output: browser autoplay rules apply to whichever audio library the project uses; unlock from a user gesture.
  • background: the Ticker follows animation frames, which hidden tabs throttle. Clamp catch-up after visibility returns.
  • release: destroy() options decide whether textures go with a display object. A consumer must not destroy a texture that another consumer still uses. Pool frequently spawned sprites/effects instead of creating them per hit, and use the installed version's particle container for large counts.
  • overlays: container order and zIndex (with sorting enabled on the parent) keep flashes beneath HUD-critical elements.

Display objects are presentation. Gameplay collision uses an explicit AABB/SAT/custom graph or physics integration, not the scene graph itself.

Accept

Record PixiJS version, shared/private ticker choice, configured logical loop (if any) and collision owner. Test variable frame cadence, stop/start/visibility recovery and per-actor hitstop without freezing unrelated actors; distinguish logical determinism from display latency.

Record the lifecycle hooks and resource release points used. A burst, teardown and background/resume cycle returns live effect, voice, timer and handle counts to the warm-up baseline; untested platforms remain not-run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.