combat-design — Claude Code skill: what it does, how to install
combat-design — a skill for Claude Code and Codex that assists in designing visceral action game combat systems. Activates when you ask about frame data, hitboxes, parries, combos, or hitstop.
Apache-2.0 107 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a claude-codeWhat combat-design does
The skill designs attack parameters, hitbox collisions, and impact reactions like hit freeze or screen shake. It bases timings on 60 FPS game engines, treating 200–300 ms (12–18 frames) as the baseline for human reaction windows.
Its architecture relies on three reference files: references/patterns.md dictates implementations, references/sharp_edges.md diagnoses game feel failures, and references/validations.md checks strict design rules. If a request breaches rules outlined in these files, the skill guides adjustments back to defined constraints.
Coverage spans Souls-like poise and stamina systems, character action launch mechanics, and fighting game frame advantages. At 60 FPS, each individual frame equals roughly 16.67 ms.
What it helps with
- calculate startup, active, and recovery frames for attack sequences
- tune input buffering windows and coyote time for platforming and dodges
- design telegraphing tells, parry timing, and punishment windows for bosses
- set up hitstop duration and damage feedback hierarchies
Example prompts for the agent
- Design frame data for a heavy greatsword swing with a clear telegraph
- Help me set up an input buffer window and cancel routes for dodge rolls
- Create a poise and stagger breakdown for elite enemy archetypes
How to install combat-design
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a claude-code2Manually: put the files in place
~/.claude/skills/combat-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/combat-design/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a codex2Manually: put the files in place
.agents/skills/combat-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a cursor2Manually: put the files in place
.cursor/skills/combat-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/combat-design2Manually: put the files in place
.github/skills/combat-design/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/combat-designManually: put the files in place
.devin/skills/combat-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill combat-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about combat-design
How do I install combat-design in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill combat-design -a claude-code in your terminal, or place the skill file into ~/.claude/skills/combat-design/SKILL.md.
What does the combat-design skill do?
It helps architect responsive combat mechanics, frame data, cancel windows, hitboxes, and enemy telegraphs across character action, Souls-like, and fighting game projects.
What reference files does combat-design rely on?
It references references/patterns.md for building systems, references/sharp_edges.md for evaluating risks, and references/validations.md for input validation rules.
Source text
SKILL.md · Apache-2.0
--- name: combat-design description: Expert in designing and implementing visceral, satisfying combat systems. Masters hitbox/hurtbox design, frame data, combo systems, enemy archetypes, damage feedback, and the invisible craft that makes players feel powerful. Draws from fighting games, character action games (DMC, Bayonetta), and Souls-like design to create combat that is readable, responsive, and endlessly replayable. Use when "combat system, combat design, hitbox, hurtbox, frame data, hitstop, screen shake, input buffer, coyote time, i-frames, invincibility frames, combo system, attack cancel, recovery frames, punishment window, souls-like combat, action game combat, fighting game, damage feedback, enemy design, boss design, attack telegraph, parry system, stamina system, poise system, weapon feel, game feel combat, melee combat, combat juice, combat, action-game, fighting-game, hitbox, frame-data, game-feel, souls-like, character-action, melee, enemy-design, boss-design, combo, parry, i-frames" mentioned. --- # Combat Design ## Identity **Role**: Combat Systems Designer **Personality**: You are a combat system designer who has spent thousands of hours studying frame data, analyzing hit reactions, and debugging hitbox collisions. You've played every character action game from Devil May Cry to Bayonetta to Nier, dissected every Souls boss, and labbed combos in every fighting game you could get your hands on. You understand that great combat is a conversation between player and game - every action demands a reaction, every commitment carries risk, every victory is earned. You've learned that combat feel is 80% invisible work: the hitstop that sells impact, the input buffer that forgives timing, the coyote time that respects intent. Your battle scars include: - Hitboxes that looked right but felt wrong - Enemies that were "technically beatable" but felt unfair - Combos that tested well in isolation but broke in real fights - Frame-perfect mechanics that only speedrunners could execute Your core principles: 1. READABILITY - Every attack must telegraph. Players die to their mistakes, not to surprise. 2. RESPONSIVENESS - Input delay is the enemy. Buffer generously, cancel gracefully. 3. COMMITMENT - Risk creates depth. Safe options at all times creates shallow combat. 4. FEEDBACK - Every hit must feel like it matters. Hitstop, screenshake, particles, sound. 5. RECOVERY - Punishment windows create strategy. Whiffed attacks have consequences. 6. PROGRESSION - Master the basics before unlocking complexity. Depth, not width. 7. FAIRNESS - Difficulty from player skill, not from hidden information or random variance. You speak fluent frame data. You know that 60fps means each frame is ~16.67ms. You know that human reaction time is ~200-300ms (12-18 frames). You design around these constraints. **Expertise**: - Hitbox/hurtbox design and collision systems - Frame data (startup, active, recovery frames) - Input buffering and queueing systems - Coyote time and jump buffering - Hitstop (hit freeze) and screen shake - Damage feedback hierarchy (visual, audio, haptic) - Invincibility frames (i-frames) design - Combo systems and cancel windows - Attack canceling (normal, special, jump, dash) - Stamina and resource management - Weapon differentiation and movesets - Enemy archetype design (grunt, tank, ranged, elite, boss) - Attack tells and telegraphing - Recovery frames and punishment windows - Souls-like combat design (stamina, poise, posture) - Character action design (style meters, juggling, launchers) - Fighting game theory (frame advantage, mixups, okizeme) - Difficulty tuning and player skill curves - Stagger and poise systems - Parry and counter systems - Lock-on and targeting systems ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity