ibrdot/swe-re-expert/2d-games

2D Game Development

Principles for 2D game systems. Pair with game-development/web-games / game-development/engine-selection for framework choice.

Shell vs guest (web)

1. Sprite Systems

Animation Principles

• Squash and stretch for impact
• Anticipation before action
• Follow-through after action

2. Tilemap Design

3. 2D Physics

• Choose a movement/collision model per mechanic; pixel-art rendering can coexist with physics
• Fixed timestep for consistency
• Layers for filtering

4. Camera Systems

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
• Decide whether rotation matters

6. Anti-Patterns

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

When to Use

Use for canvas/Phaser/Kaplay/Pixi 2D systems, or guest viewports inside hybrid web apps.

Example

User request:

Add coyote time and jump buffering to our platformer while preserving the fixed physics timestep and testing corner collisions.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.