Our review
This skill provides principles for 2D game development, covering sprites, tilemaps, physics, camera systems, and genre patterns.
Strengths
- Clear explanation of sprite systems and animation principles like squash and stretch
- Practical advice on tilemap design and parallax layers
- Guidance on collision shapes suitable for different objects
- Presentation of anti-patterns to avoid common mistakes
Limitations
- Does not provide executable code or integration with a specific engine
- Advanced topics like performance optimization are not detailed
- Assumes basic programming knowledge for games
Use this skill when you need structured guidance for designing or implementing 2D game systems, whether for a new project or improving an existing one.
Avoid this skill if you are looking for a step-by-step tutorial with framework-specific code, or if you are working on a 3D game.
Security analysis
SafeThe skill provides educational content on 2D game development principles with no executable commands, network access, or data exfiltration risks. Allowed tools are limited to file operations, and the content is purely informational.
No concerns found
Examples
I want to create a 2D tilemap with background, terrain, props, and foreground layers. Each layer has different tiles. How should I organize the tileset and implement auto-tiling for terrain? Also, consider collision shapes for the terrain layer.I need a camera system for my 2D platformer that follows the player with a look-ahead effect. The camera should smoothly transition and have screen shake on impact. Provide guidance on implementing this.I'm designing a 2D platformer character controller. I want to implement coyote time (allowing jumps shortly after leaving a ledge) and jump buffering (allowing jumps shortly before landing). How should I code these mechanics?name: 2d-games description: 2D game development principles. Sprites, tilemaps, physics, camera. allowed-tools: Read, Write, Edit, Glob, Grep
2D Game Development
Principles for 2D game systems.
1. Sprite Systems
Sprite Organization
| Component | Purpose | |-----------|---------| | Atlas | Combine textures, reduce draw calls | | Animation | Frame sequences | | Pivot | Rotation/scale origin | | Layering | Z-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
| Factor | Recommendation | |--------|----------------| | Size | 16x16, 32x32, 64x64 | | Auto-tiling | Use for terrain | | Collision | Simplified shapes |
Layers
| Layer | Content | |-------|---------| | Background | Non-interactive scenery | | Terrain | Walkable ground | | Props | Interactive objects | | Foreground | Parallax overlay |
3. 2D Physics
Collision Shapes
| Shape | Use Case | |-------|----------| | Box | Rectangular objects | | Circle | Balls, rounded | | Capsule | Characters | | Polygon | Complex shapes |
Physics Considerations
- Pixel-perfect vs physics-based
- Fixed timestep for consistency
- Layers for filtering
4. Camera Systems
Camera Types
| Type | Use | |------|-----| | Follow | Track player | | Look-ahead | Anticipate movement | | Multi-target | Two-player | | Room-based | Metroidvania |
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 textures | Use atlases | | Complex collision shapes | Simplified collision | | Jittery camera | Smooth following | | Pixel-perfect on physics | Choose one approach |
Remember: 2D is about clarity. Every pixel should communicate.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.