Skip to content
cccskills
FreePublished on GitHub

2d-games

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

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

3D game development principles. Rendering, shaders, physics, cameras.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

The English summary is being prepared. Showing the original description.

umairinayat/Specter-AI19Updated Sep 29, 2026

See all skills by umairinayat

Report a problem with this skill