2d-games_skill

This skill helps you design and implement clear 2D game systems, including sprites, tilemaps, physics, and camera, for polished gameplay.
  • TypeScript

5.7k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vudovn/antigravity-kit --skill 2d-games

  • SKILL.md2.1 KB

Overview

This skill distills practical principles for 2D game development, covering sprites, tilemaps, physics, and camera systems. It highlights common patterns and anti-patterns to help you build clear, performant 2D games. Use it to guide architecture choices and iterate faster on gameplay feel.

How this skill works

The skill inspects core subsystems: sprite organization and animation, tilemap layout and collision, 2D physics shapes and timesteps, and camera behaviors like follow and room-based systems. It recommends concrete configurations (tile sizes, FPS ranges, collision shape choices) and runtime practices (fixed timestep, layer filtering). It also flags common anti-patterns and offers genre-specific tweaks for platformers and top-down games.

When to use it

  • Starting a new 2D project and choosing art and physics workflows
  • Refactoring draw calls and texture use to improve performance
  • Designing tilemaps, collision, and layering for levels
  • Tuning player feel: jump behavior, coyote time, and camera follow
  • Implementing multiplayer or split-screen multi-target cameras

Best practices

  • Pack textures into atlases to reduce draw calls and simplify batching
  • Choose tile sizes (16/32/64) early and stick to a consistent grid
  • Prefer simplified collision shapes (box/circle/capsule) over complex polygons
  • Use a fixed timestep for physics and interpolate visuals for smoothness
  • Keep camera movement smooth and limit screen shake to short, diminishing bursts

Example use cases

  • Optimize sprite rendering by moving from separate textures to a unified atlas
  • Build auto-tiling terrain with layered tilemaps for background, terrain, and foreground
  • Implement platformer controls with coyote time, jump buffering, and variable jump height
  • Create a camera that follows the player with look-ahead and soft damping to reduce jitter
  • Design collision for a top-down shooter using circle shapes for projectiles and capsule for characters

FAQ

Pick 16, 32, or 64 based on art detail and camera zoom; smaller tiles give finer detail but increase map complexity.

When should I use pixel-perfect collisions?

Use pixel-perfect only when gameplay requires exact hit detection; otherwise prefer physics-based or simplified shapes for performance and stability.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
2d-games skill by vudovn/antigravity-kit | VeilStrat