godot-ability-system — Claude Code skill for Godot abilities

What godot-ability-system does

The skill lays out how to structure ability systems for RPGs and action games in Godot. Live cooldowns, the global cooldown and execute() calls belong in a scene-scoped manager under the caster, not in a global Autoload, because a global cast oracle breaks encapsulation and multiplayer authority. An Autoload is fine for unlock ranks and flags only.

It ships GDScript files: ability_resource.gd holds data plus a virtual execute(), ability_manager.gd and ability_container.gd cover the two scene-scoped manager styles, combo_tracker.gd handles windowed chains, charge_ability.gd covers multi-charge recharges, and skill_node.gd with skill_tree_manager.gd builds prerequisite graphs. Status effects run through status_effect.gd and status_effect_manager.gd, while ability_caster_network.gd predicts locally and lets authority validate.

Cooldown ticking and status durations must run on _physics_process(delta) or Timer nodes, otherwise frame spikes throw the timings off. Status templates applied at runtime need duplicate(true) — a single shared .tres mutates for every character using it. Saving cooldowns means storing absolute end timestamps rather than leftover seconds. The deeper combo, charge and networking material sits in a separate reference file that you skip on a first AbilityResource plus manager pass.