New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Combat Animation Developer

Game dev: combat animation

by MengTo · MIT license · ★ 6,243 on GitHub · updated Sep 23

Game dev: combat animation cover

Build, fix and review character combat animations (melee strikes, bow shots, spell casts, skills, monster attacks, whole move sets) so they read like Diablo IV, Baldur's Gate 3 or Elden Ring and never stretch, lock, wring or break an…

---
name: game-dev-combat-animation
description: Build, fix and review character combat animations (melee strikes, bow shots, spell casts, skills, monster attacks, whole move sets) so they read like Diablo IV, Baldur's Gate 3 or Elden Ring and never stretch, lock, wring or break an arm, wrist or hand. A written standard with numbered rules, per-frame tests on the real skinned mesh, keys designed from upper-arm, forearm and blade intents, checks from every camera the player sees, two blind critics plus a blind A/B against the last release, and every critic claim verified against full-resolution frames and live-rig numbers. Use when creating or reworking any attack, skill or move set; when the user says arms, hands, wrists, elbows or weapons look stretched, weird, broken or wrong; when they ask for a standard, rules or tests for animations; or when they ask to score animations or get them to N out of 10.
---

# Game dev: combat animation

Distilled from the Thornvigil knight-and-archer pass (2026-09-30 to 10-01, releases 1.0.71 and 1.0.72). Its outcome:
- Arms and hands won 5 of 8 blind A/B comparisons against the previous release.
- The archer's broken anchor and the knight's frozen, straight-armed follow-through were fixed.
- Seven rounds of fixes came from traps that numbers would have caught earlier. Those traps are listed below.

Read `references/thornvigil.md` for the project's files, commands and current state, and `references/traps.md` before changing keys.

## The loop

1. **Write the standard before touching keys.** Extend `docs/combat-animation-standard.md` (or the project's equivalent) with the move's own numbered rules:
   - Phases on the game's clock: anticipation, the contact or release on the rule's frame, recovery.

Overview

Distilled from the Thornvigil knight-and-archer pass (2026-09-30 to 10-01, releases 1.0.71 and 1.0.72). Its outcome: - Arms and hands won 5 of 8 blind A/B comparisons against the previous release. - The archer's broken anchor and the knight's frozen, straight-armed follow-through were fixed. - Seven rounds of fixes came from traps that numbers would have caught earlier. Those traps are listed below.

Manual install (npx, ZIP)
Claude Codenpx skills add MengTo/Skills --skill game-dev-combat-animation -g -a claude-code
Claude Code (degit)npx degit MengTo/Skills/agent-skills/game-combat/game-dev-combat-animation#main ~/.claude/skills/game-dev-combat-animation
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.8 KB
Read SKILL.md here
MengTo/main1 file shown
SKILL.md
Show the full text93 lines

Game dev: combat animation

Distilled from the Thornvigil knight-and-archer pass (2026-09-30 to 10-01, releases 1.0.71 and 1.0.72). Its outcome:

  • Arms and hands won 5 of 8 blind A/B comparisons against the previous release.
  • The archer's broken anchor and the knight's frozen, straight-armed follow-through were fixed.
  • Seven rounds of fixes came from traps that numbers would have caught earlier. Those traps are listed below.

Read references/thornvigil.md for the project's files, commands and current state, and references/traps.md before changing keys.

The loop

  1. Write the standard before touching keys. Extend docs/combat-animation-standard.md (or the project's equivalent) with the move's own numbered rules:
    • Phases on the game's clock: anticipation, the contact or release on the rule's frame, recovery.
    • Body mechanics, weapon path, camera reads.
    • Mark each rule test (measured) or reviewed (scored from frames).
    • Ground every rule in a real reference: a Tripo Studio motion-capture preset for body mechanics, or coached technique such as the archery shot cycle. Use Tripo presets only; the user has no Mixamo account and declined Quaternius.
  2. Baseline first. Capture both surfaces (the Characters page and in play), keep the frames, and get blind scores before changing anything.
  3. Design keys from anatomy, not from hand positions. For each key pick the upper-arm direction u, the forearm direction f and the blade b, then run keydesign.mjs. It returns the hand target and flags:
    • raise over 100°;
    • flex outside 12–140°;
    • a blade outside 25–115° off the forearm. Hand keys ride the shoulder; blade and elbow keys are world directions. See references/techniques.md.
  4. Measure before looking. Bake, then:
    • armcheck.mjs for joint ranges and the skin's stretch and crush per arm region on the real mesh;
    • at.mjs for the fist and blade at given times;
    • the move's own probe: knight-measure.mjs, anchor.mjs or drawfit.mjs. Fix numbers that break a rule before spending a capture.
  5. Test. Run the arm-ranges test and the move's tests. When you add a test for a bug, temporarily restore the bug and prove the test fails; a test that reads the same wrong convention as the code passes forever.
  6. Capture both cameras and look yourself at full resolution. A pose that reads well from the front can read broken from the game camera, and the reverse. Diff each capture against the previous round to be sure it is new.
  7. Judge. Use two blind critics with a fixed rubric (5 criteria × 0–2; the lower score counts) and a blind A/B against the last release with identical sheet titles. Then verify every claim against full-resolution frames and live-rig numbers before acting on it. See references/review.md and templates/.
  8. Ship by the project's rules: tests, build, changelog with real screenshots, push, sizes, publish. Use the workflow-ship-change skill. If a pushed but unpublished release regresses, correct it in place with a follow-up commit; don't add a version for something players never saw.
  9. Show it. When asked for videos, capture at 30 fps on the move's own clock, place the Characters page and in-play views side by side, and play real speed then quarter speed (vidcompose.py + encode.swift).

The arm and hand rules

The rig has no twist or corrective bones; past these ranges the skin visibly wrings, crushes or stretches. Every frame of every strike stays inside them, on both bodies, measured on the real skinned mesh.

Rule Limit
Elbow flexion 10–152°; the striking or drawing arm keeps ≥20° through the middle 80% of the move
Contact reach sword hand ≥60% of arm length from the shoulder at contact (reach into the blow, never lock)
Wrist bend ≤50°, roll ≤45°; sword wrist capped at 40°; a drawing hand held straight
Twist forearm roll ≤52°, upper-arm roll ≤52°
Raise ≤105° from hanging (shoulder skin crushes beyond); no overhead raises
Skin the worst 1% of each arm or hand region's edges: stretch ≤2×, crush ≤3× against the bind
Hands always in a pose: fist on a grip, hook on a string (set → loose → follow-through), relaxed when empty; never splayed or clawed
Paths hands ride their shoulders and arc about them between keys; blade keys stay reachable (25–115° off the forearm)

Full rules, with the reasons and the tests that enforce them, are in references/rules.md.

Techniques that worked

  • Shoulder-relative hands with arc interpolation. A fixed hand target that the lunging trunk drives the shoulder into crushes the arm, and a straight-line lerp folds the elbow shut mid-way.
  • Aim the forearm, not the wrist. With the wrist capped, the blade lands on the cone the forearm roll allows. To change the blade, change f.
  • Read blade keys in world space. With the trunk wound back about 70°, "over the sword shoulder" points across behind the head. Tilt the chamber tip-up so it reads as a diagonal.
  • Keep the follow-through moving.
    • Quick cut: carry the hand down past the shield-side hip on a bent elbow, with the blade still on the line.
    • Heavy cut: sink across, then rebound with the elbow folding.
    • Never hold an arm out at the foe with the blade hanging.
  • Bow draw. Anchor under the jaw beside the chin, where the hand stays in sight from both cameras. The draw elbow rides 6–8 cm under the arrow. Turn the hips side-on, which fixed draw-shoulder crush better than shrug or elbow poles. Hold the hook through the loose, then send the hand out past the shoulder rather than round the head.
  • Kinetic chain. Hips lead the chest, and the chest leads the arm. A bow's recoil answers the loose and never leads it.

Traps that each cost a round

references/traps.md has symptom → cause → fix for each. The short list:

  • Bone axes. The HumGen head bone is +Y forward and +Z down. Check any bone-local offset against mesh landmarks (face.mjs).
  • Masked failures. The first failing assertion hides every later move in the same test loop, and the first failing gender hides the other.
  • Camera reads.
    • A hand by the neck reads as "behind the head" from the game camera.
    • A blade pointing at the camera reads as "hanging".
    • An elbow bent in the view plane reads as straight.
  • Critic misreads. Thumbnails mislead critics. Check full-resolution frames and the live rig before changing anything.
  • Capture traps.
    • Never edit src while a capture runs.
    • After location.reload(), wait before evaluating the next script.
    • Hand-stepped frames are not FPS measurements.

Report

Lead with what changed in the moves and whether it is live. Then give:

  • a scores table: before → after, lower of the two critics, per surface;
  • the A/B result;
  • the faults still open, named by frame;
  • the tests added;
  • file and push sizes.

Say plainly when a score sits short of the target and why.

1---
2name: game-dev-combat-animation
3description: Build, fix and review character combat animations (melee strikes, bow shots, spell casts, skills, monster attacks, whole move sets) so they read like Diablo IV, Baldur's Gate 3 or Elden Ring and never stretch, lock, wring or break an arm, wrist or hand. A written standard with numbered rules, per-frame tests on the real skinned mesh, keys designed from upper-arm, forearm and blade intents, checks from every camera the player sees, two blind critics plus a blind A/B against the last release, and every critic claim verified against full-resolution frames and live-rig numbers. Use when creating or reworking any attack, skill or move set; when the user says arms, hands, wrists, elbows or weapons look stretched, weird, broken or wrong; when they ask for a standard, rules or tests for animations; or when they ask to score animations or get them to N out of 10.
4---
5 
6# Game dev: combat animation
7 
8Distilled from the Thornvigil knight-and-archer pass (2026-09-30 to 10-01, releases 1.0.71 and 1.0.72). Its outcome:
9- Arms and hands won 5 of 8 blind A/B comparisons against the previous release.
10- The archer's broken anchor and the knight's frozen, straight-armed follow-through were fixed.
11- Seven rounds of fixes came from traps that numbers would have caught earlier. Those traps are listed below.
12 
13Read `references/thornvigil.md` for the project's files, commands and current state, and `references/traps.md` before changing keys.
14 
15## The loop
16 
171. **Write the standard before touching keys.** Extend `docs/combat-animation-standard.md` (or the project's equivalent) with the move's own numbered rules:
18 - Phases on the game's clock: anticipation, the contact or release on the rule's frame, recovery.
19 - Body mechanics, weapon path, camera reads.
20 - Mark each rule **test** (measured) or reviewed (scored from frames).
21 - Ground every rule in a real reference: a Tripo Studio motion-capture preset for body mechanics, or coached technique such as the archery shot cycle. Use Tripo presets only; the user has no Mixamo account and declined Quaternius.
222. **Baseline first.** Capture both surfaces (the Characters page and in play), keep the frames, and get blind scores before changing anything.
233. **Design keys from anatomy, not from hand positions.** For each key pick the upper-arm direction `u`, the forearm direction `f` and the blade `b`, then run `keydesign.mjs`. It returns the hand target and flags:
24 - raise over 100°;
25 - flex outside 12–140°;
26 - a blade outside 25–115° off the forearm.
27 Hand keys ride the shoulder; blade and elbow keys are world directions. See `references/techniques.md`.
284. **Measure before looking.** Bake, then:
29 - `armcheck.mjs` for joint ranges and the skin's stretch and crush per arm region on the real mesh;
30 - `at.mjs` for the fist and blade at given times;
31 - the move's own probe: `knight-measure.mjs`, `anchor.mjs` or `drawfit.mjs`.
32 Fix numbers that break a rule before spending a capture.
335. **Test.** Run the arm-ranges test and the move's tests. When you add a test for a bug, temporarily restore the bug and prove the test fails; a test that reads the same wrong convention as the code passes forever.
346. **Capture both cameras and look yourself at full resolution.** A pose that reads well from the front can read broken from the game camera, and the reverse. Diff each capture against the previous round to be sure it is new.
357. **Judge.** Use two blind critics with a fixed rubric (5 criteria × 0–2; the lower score counts) and a blind A/B against the last release with identical sheet titles. Then **verify every claim** against full-resolution frames and live-rig numbers before acting on it. See `references/review.md` and `templates/`.
368. **Ship** by the project's rules: tests, build, changelog with real screenshots, push, sizes, publish. Use the `workflow-ship-change` skill. If a pushed but unpublished release regresses, correct it in place with a follow-up commit; don't add a version for something players never saw.
379. **Show it.** When asked for videos, capture at 30 fps on the move's own clock, place the Characters page and in-play views side by side, and play real speed then quarter speed (`vidcompose.py` + `encode.swift`).
38 
39## The arm and hand rules
40 
41The rig has no twist or corrective bones; past these ranges the skin visibly wrings, crushes or stretches. Every frame of every strike stays inside them, on both bodies, measured on the real skinned mesh.
42 
43| Rule | Limit |
44|---|---|
45| Elbow flexion | 10–152°; the striking or drawing arm keeps ≥20° through the middle 80% of the move |
46| Contact reach | sword hand ≥60% of arm length from the shoulder at contact (reach into the blow, never lock) |
47| Wrist | bend ≤50°, roll ≤45°; sword wrist capped at 40°; a drawing hand held straight |
48| Twist | forearm roll ≤52°, upper-arm roll ≤52° |
49| Raise | ≤105° from hanging (shoulder skin crushes beyond); no overhead raises |
50| Skin | the worst 1% of each arm or hand region's edges: stretch ≤2×, crush ≤3× against the bind |
51| Hands | always in a pose: fist on a grip, hook on a string (set → loose → follow-through), relaxed when empty; never splayed or clawed |
52| Paths | hands ride their shoulders and arc about them between keys; blade keys stay reachable (25–115° off the forearm) |
53 
54Full rules, with the reasons and the tests that enforce them, are in `references/rules.md`.
55 
56## Techniques that worked
57 
58- **Shoulder-relative hands with arc interpolation.** A fixed hand target that the lunging trunk drives the shoulder into crushes the arm, and a straight-line lerp folds the elbow shut mid-way.
59- **Aim the forearm, not the wrist.** With the wrist capped, the blade lands on the cone the forearm roll allows. To change the blade, change `f`.
60- **Read blade keys in world space.** With the trunk wound back about 70°, "over the sword shoulder" points across behind the head. Tilt the chamber tip-up so it reads as a diagonal.
61- **Keep the follow-through moving.**
62 - Quick cut: carry the hand down past the shield-side hip on a bent elbow, with the blade still on the line.
63 - Heavy cut: sink across, then rebound with the elbow folding.
64 - Never hold an arm out at the foe with the blade hanging.
65- **Bow draw.** Anchor under the jaw beside the chin, where the hand stays in sight from both cameras. The draw elbow rides 6–8 cm under the arrow. Turn the hips side-on, which fixed draw-shoulder crush better than shrug or elbow poles. Hold the hook through the loose, then send the hand out past the shoulder rather than round the head.
66- **Kinetic chain.** Hips lead the chest, and the chest leads the arm. A bow's recoil answers the loose and never leads it.
67 
68## Traps that each cost a round
69 
70`references/traps.md` has symptom → cause → fix for each. The short list:
71- **Bone axes.** The HumGen `head` bone is +Y forward and +Z down. Check any bone-local offset against mesh landmarks (`face.mjs`).
72- **Masked failures.** The first failing assertion hides every later move in the same test loop, and the first failing gender hides the other.
73- **Camera reads.**
74 - A hand by the neck reads as "behind the head" from the game camera.
75 - A blade pointing at the camera reads as "hanging".
76 - An elbow bent in the view plane reads as straight.
77- **Critic misreads.** Thumbnails mislead critics. Check full-resolution frames and the live rig before changing anything.
78- **Capture traps.**
79 - Never edit `src` while a capture runs.
80 - After `location.reload()`, wait before evaluating the next script.
81 - Hand-stepped frames are not FPS measurements.
82 
83## Report
84 
85Lead with what changed in the moves and whether it is live. Then give:
86- a scores table: before → after, lower of the two critics, per surface;
87- the A/B result;
88- the faults still open, named by frame;
89- the tests added;
90- file and push sizes.
91 
92Say plainly when a score sits short of the target and why.
93 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 6,243
Checked
Source
MengTo/Skills ↗
Creator
MengTo · 6 listings
View creator

Similar skills

See all →
Motion Effect Glossaryemilkowalski/skills · by emilkowalskiReverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.★ 40.8k GitHub starsWatercolor Animation Generatoredenfunf/reelmimic · by edenfunfMake hand-painted watercolour-and-ink cartoon videos (MP4) with code — p5.js + p5.brush rendered frame by frame in headless Chrome, encoded with ffmpeg — starring Clawd or any character. Use when the user asks to make an animation, animated short, cartoon, music video, lyric video, animated GIF/loop or "a video of Clawd…", or mentions the PDoomVideo / ClaudeAnimationBase approach. Covers storyboarding, the engine API, the render-and-look review loop, music/lyric sync and splitting long videos across subagents.★ 3.6k GitHub starsModern Web ReferenceGoogleChrome/modern-web-guidance · by GoogleChromeSearch tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.★ 2.4k GitHub starsTailwind UI Componentsnextlevelbuilder/ui-ux-pro-max-skill · by nextlevelbuilderCreate beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.★ 130k GitHub starsWeb-to-Native Mobile Optimizeremilkowalski/skills · by emilkowalskiMake a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or reviewed on mobile, when something "works in Chrome but feels wrong on my phone", when building a PWA, a bottom sheet, a carousel, a full-screen layout, or any touch interaction. For motion itself use animate; for React Native use animate-expo.★ 40.8k GitHub starsAnimation Opportunity Scoutemilkowalski/skills · by emilkowalskiSearch a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.★ 40.8k GitHub stars

More from MengTo

Gradient Border DesignerMengTo/Skills · by MengToApply subtle gradient-border treatments for premium web surfaces. Use when cards, pricing panels, nav bars, modals, buttons, or hero surfaces need a refined edge highlight without a loud glow.★ 6.2k GitHub starsThree.js Scroll BuilderMengTo/Skills · by MengToBuild rich, scroll-controlled real-time Three.js experiences as one persistent 3D world whose camera, lighting, atmosphere, materials, objects, DOM story, and interactions evolve across authored chapters. Use for 3D scrollytelling, scroll-driven WebGL worlds, camera journeys, interactive portfolios, product stories, exhibitions, explainers, game or film microsites, spatial narratives, and multi-scene websites where native scroll should travel through one continuous place. Not limited to landing pages.★ 6.2k GitHub starsCombat Skill Quality ScorerMengTo/Skills · by MengToScore a game's combat skills and spells out of 10 with blind judges, then raise the weakest to a bar, for timing and readability (does a skill read as itself, does the blow land when it lands) and for art (detail, light, trails, impact, art direction, judged against a reference such as Diablo IV). Covers filming casts on a stopped, stepped clock, contact strips and close-ups, anonymised two-judge rounds, the levers that moved scores (hero props made from a painted concept with image-to-3D, own schedules and keyed moves, painted additive textures, camera-facing ribbons, light outside the body), the traps that cost points, asset and load budgets, and shipping each skill as its own version. Use when the user asks to score, review, improve, polish or rebuild combat skills, spells or attacks; says a skill "doesn't make sense", "looks bad" or should look like another game; names a target score; or starts a "next skill" thread. Project specifics (review hooks, harness settings, where each skill's code lives, scores so far) go in an optional local references/<project>.md next to this skill.★ 6.2k GitHub starsCursor Trail GeneratorMengTo/Skills · by MengToBuild a cursor trail whose spacing stays constant at any hand speed, by emitting motes per unit of distance travelled rather than on a timer, so a flick draws the same continuous ribbon as a crawl instead of breaking into scattered dots. Covers sub-segment placement, the ring-buffer ordering trap, the idle breath a distance emitter needs, anchoring the trail to the screen in a 3-D scene, scaling scatter against the plane it hangs on, coasting instead of stopping dead, touch and reduced-motion fallbacks, and why moving the emitter to a DOM overlay to raise its z-index costs more than it buys. Use for cursor wisps, pointer sparks, embers, magic trails, comet tails, plankton, dust, or any mote trail that must stay legible however fast the hand moves.★ 6.2k GitHub starsCinematic Scroll DesignerMengTo/Skills · by MengToTurn an article, case study, brand narrative, product journey, or long-form story into a cinematic scroll-driven landing page using one of three renderers: scrubbed video, a real-time Three.js world, or semantic HTML/SVG data and typography. Use when the user asks for a scroll world, fly-through landing page, article-to-website transformation, animated planet, data scrollytelling, video-scrubbed page, connected visual journey, or story-led alternative to ordinary stacked sections.★ 6.2k GitHub stars