game-dev-combat-skill-polish
Installation
SKILL.md
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.