Game Dev Combat Skill Polish
Score a game's combat skills and spells out of 10 with blind judges, then raise the...
Install
npx skills add MengTo/Skills --skill game-dev-combat-skill-polish -g -a claude-code -y- Repository
- MengTo/Skills7.2k
- Category
- Media
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,087 tokens
- Runs scripts
- Yes, review before use
What it does
Score 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.
Game dev: combat skill polish
A skill is the cast (the caster's body), the effect (what it throws, raises or tears open), and the result (the target's reaction and what it leaves behind). Polish all three, judged from real footage by people who did not make it.
There are two bars. Know which one the user means:
| Bar | Asks | Rubric | Typical target |
|---|---|---|---|
| Readability | Does it read as itself? Does the result land when and where the blow arrives? Is the pose its own? | references/rubric-readability.md (reads, timing, body, effect, reaction) | every skill 6+ |
| Art | Detail and texture, light, motion and trails, impact, art direction, against a named reference | references/rubric-art.md (Diablo IV paladin skills, described in words) | 7+ per skill |
A skill can score 7 on readability and 3 on art. Never quote a score without naming its rubric.
1. Pin down the job
- Which skills: all of them (a survey), or named ones (a rebuild). One skill per thread when several run at once.
- The bar and the reference. If the user shows a reference image, save it into the project so judges can open it; otherwise describe it in words in the rubric.
- Read the project reference first (
references/<project>.md, if there is one): where each skill's code lives, the harness settings, the scorecard so far, and what other threads already learned. - Before designing,
git fetchand check what other threads are changing; several skill threads edit the same effect and animation files.
