gameplay-programmer

Implement gameplay mechanics with tuning surfaces and state management.

Updated May 18, 2026
One-click install
npx skills add https://github.com/afovea/game-dev-skills --skill gameplay-programmer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gameplay-programmer
Source: https://github.com/afovea/game-dev-skills/tree/main/plugins/game-team/skills/gameplay-programmer
Command: npx skills add https://github.com/afovea/game-dev-skills --skill gameplay-programmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the gap between high-level design concepts and reliable, performant implementation, ensuring that gameplay mechanics are debuggable, tunable, and maintainable.

Core Features & Use Cases

  • Mechanic Implementation: Translates design specs into functional code with clear tuning surfaces and state management.
  • System Architecture: Designs multi-component systems with defined data flow, ownership, and save/network implications.
  • Use Case: When a designer requests a new dodge mechanic, this skill provides a structured implementation plan including animation hooks, input buffering, and a tuning surface for designers to adjust feel without touching code.

Quick Start

Use the gameplay-programmer skill to design a state machine and tuning surface for a new dash mechanic with coyote time.

Frequently Asked Questions about gameplay-programmer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement gameplay mechanics with explicit tuning surfaces for designers?

To implement gameplay mechanics with tuning surfaces, translate design specs into functional code with defined state management and clear parameters. This allows designers to adjust game feel without touching the underlying code.

How do I structure a character controller with input buffering and coyote time?

Structuring a character controller with input buffering involves designing a state machine that processes animation hooks and input windows. This provides a responsive dodge or dash mechanic with adjustable timing surfaces.

Can I use this approach to design AI behaviors across diverse game engines?

Yes, you can design AI behaviors across diverse game engines by bridging design requirements with technical constraints. This approach facilitates system architecture, debugging, and refactoring within your specific project architecture.

What is the best way to refactor gameplay code for better debug visibility?

The best way to refactor gameplay code for debug visibility is to design multi-component systems with defined data flow and ownership. This ensures code health and maintainability across animation, audio, and network systems.

How do I manage data flow and ownership when designing multi-component gameplay systems?

Managing data flow and ownership in multi-component gameplay systems requires defining explicit integration points for animation, audio, and network systems. This architecture ensures mechanics are debuggable, tunable, and maintainable.