SkillAgentSearch skills...

build-threejs-enemy-systems

Build or refactor reusable, data-driven enemy archetype and moveset systems for Three.js action games. Use for enemy content schemas, model and rig conventions, combat move timing and contact contracts, runtime state boundaries, placeholder fallbacks, deterministic fixtures, or production playthroug…

Install / Use

npx skills add MengTo/Skills --skill build-threejs-enemy-systems

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Legal

Supported Platforms

Universal

Tags

Our assessment of build-threejs-enemy-systems

build-threejs-enemy-systems scores 83/100 on our quality scale, 155th of 209 Legal skills we index.

Its SKILL.md is 4.3 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so build-threejs-enemy-systems is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

build-threejs-enemy-systems compared with similar skills

All 4 of these similar skills score higher than build-threejs-enemy-systems; compare them before choosing.

SkillScoreStarsUpdatedFormat
build-threejs-enemy-systems (this skill)by MengTo836.3k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install build-threejs-enemy-systems?
Run npx skills add MengTo/Skills --skill build-threejs-enemy-systems. The install tabs above show the steps for each supported agent.
Which AI agents does build-threejs-enemy-systems work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is build-threejs-enemy-systems safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is build-threejs-enemy-systems still maintained?
The repository was last updated about 2 months ago, so build-threejs-enemy-systems is actively maintained.

name: build-threejs-enemy-systems description: Build or refactor reusable, data-driven enemy archetype and moveset systems for Three.js action games. Use for enemy content schemas, model and rig conventions, combat move timing and contact contracts, runtime state boundaries, placeholder fallbacks, deterministic fixtures, or production playthrough validation.

Build Three.js Enemy Systems

Make each enemy a portable authored definition consumed by shared runtime systems. Keep AI choice, combat resolution, rendering, and feedback as separate consumers of the same stable contract.

Separate content from runtime state

  • Put stable IDs, role/tags, base stats, presentation spec, move IDs, AI hints, feedback hook IDs, rewards, and variant data in immutable authored definitions.
  • Put instance ID, transform, health/posture, target, current move and phase clock, cooldowns, statuses, pathing, visibility, and LOD state in runtime instances.
  • Reference definitions by ID. Reject duplicate IDs, missing references, invalid ranges, or impossible timing during content validation.
  • Never mutate authored definitions, store live timers in content, or duplicate the combat clock across AI, animation, and rendering.

Normalize presentation contracts

Define these fields before integrating a model:

  • source or factory ID, provenance, coordinate system, forward axis, and meters-per-unit;
  • root pivot at ground contact, normalized scale, facing offset, and visual height;
  • simple movement collider plus named hurtboxes, independent of render geometry;
  • stable sockets for contact origins, weapons, projectiles, VFX, audio, UI markers, and targeting;
  • rig and semantic clip map for idle, locomotion, moves, reactions, and death;
  • LOD tiers with hysteresis, animation/update policy, and unchanged gameplay colliders.

Normalize at the asset boundary. Do not scatter scale fixes, pivot offsets, raw clip names, or compensating rotations through gameplay code.

Define moves as data

For every move, define:

  • stable ID, AI tags, eligibility range/angle/line-of-sight, weight, and state prerequisites;
  • startup and telegraph, one or more active windows, recovery, cooldown, and minimum commitment;
  • movement, facing, cancellation, armor, interrupt, stagger, and phase rules;
  • contact shape/socket, damage, posture, knockback, status, and per-target hit limits;
  • semantic animation, VFX, and audio hook IDs with cleanup rules.

Let AI select only legal move IDs; let the combat system own timing and outcomes. Resolve damage from authoritative collision/contact events using stable action and target identifiers. Apply each contact once, then drive animation, VFX, audio, and UI from the resolved event.

Provide an honest fallback

When a production model is unavailable, use a deliberate placeholder that preserves footprint, height, pivot, collider, sockets, facing, move timing, and state readability. Log the fallback once and keep it visually unmistakable. Never silently substitute a mismatched asset or call placeholder visuals production-ready.

Add a new enemy

  1. Existing archetype and moves fit? Configure a new definition; do not add runtime branches.
  2. A new behavior is essential? Add the smallest reusable move, hook, or AI tag before adding a new subsystem.
  3. Model ready? Normalize it to the shared presentation contract; otherwise use the honest fallback.
  4. Content complete? Validate references, timing, contact, cooldown, recovery, interrupts, and feedback hooks.
  5. Proof ready? Add deterministic fixtures and automated tests, then run desktop and mobile playthroughs.

Prove the system

  • Create deterministic fixtures for spawn, each move phase, wrong range/direction, obstruction, interrupt, stagger, death/reset, missing-model fallback, LOD transitions, and multiple instances sharing one definition.
  • Test content uniqueness and references, active-window boundaries, cooldown/recovery, per-target hit deduplication, lifecycle cleanup, and pause/frame-step behavior.
  • Play a representative encounter in the repository-approved browser. Confirm telegraphs, contact, state, animation, VFX/audio, targetability, and rewards agree.
  • Verify desktop and mobile camera distance, touch controls, reduced motion, console health, frame time, draw calls, memory stability, and crowded-scene LOD behavior. Report baseline failures separately.

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryLegal
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions