agentleFS
Sign inStart free
xenitV1xenitV1/Antigravity-Workflows/skills/game-development/2d-games/SKILL.md

2d-games

Skill130 starsChanged 10 months agoMITView on GitHub

2D game development principles. Sprites, tilemaps, physics, camera.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Consider rotation or not

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

2D Game Development

Principles for 2D game systems.

1. Sprite Systems

Sprite Organization

ComponentPurpose
AtlasCombine textures, reduce draw calls
AnimationFrame sequences
PivotRotation/scale origin
LayeringZ-order control

Animation Principles

  • Frame rate: 8-24 FPS typical
  • Squash and stretch for impact
  • Anticipation before action
  • Follow-through after action

2. Tilemap Design

Tile Considerations

FactorRecommendation
Size16x16, 32x32, 64x64
Auto-tilingUse for terrain
CollisionSimplified shapes

Layers

LayerContent
BackgroundNon-interactive scenery
TerrainWalkable ground
PropsInteractive objects
ForegroundParallax overlay

3. 2D Physics

Collision Shapes

ShapeUse Case
BoxRectangular objects
CircleBalls, rounded
CapsuleCharacters
PolygonComplex shapes

Physics Considerations

  • Pixel-perfect vs physics-based
  • Fixed timestep for consistency
  • Layers for filtering

4. Camera Systems

Camera Types

TypeUse
FollowTrack player
Look-aheadAnticipate movement
Multi-targetTwo-player
Room-basedMetroidvania

Screen Shake

  • Short duration (50-200ms)
  • Diminishing intensity
  • Use sparingly

5. Genre Patterns

Platformer

  • Coyote time (leniency after edge)
  • Jump buffering
  • Variable jump height

Top-down

  • 8-directional or free movement
  • Aim-based or auto-aim
  • Consider rotation or not

6. Anti-Patterns

❌ Don't✅ Do
Separate texturesUse atlases
Complex collision shapesSimplified collision
Jittery cameraSmooth following
Pixel-perfect on physicsChoose one approach

Remember: 2D is about clarity. Every pixel should communicate.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free