2d-games
sickn33/antigravity-awesome-skills
2D game development principles: sprites, tilemaps, physics, and camera systems.
What is 2d-games?
Reference guide for building 2D games covering sprite organization, tilemap design, collision physics, and camera behavior. Use this when designing or implementing core 2D game systems to follow proven patterns and avoid common pitfalls.
- Sprite atlasing and animation frame sequencing
- Tilemap layering and auto-tiling for terrain
- Collision shape selection and physics configuration
- Camera following and screen shake techniques
- Platformer mechanics (coyote time, jump buffering)
- Top-down movement and aiming patterns
How to install 2d-games
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill game-developmentHow to use 2d-games
- 1.Review the sprite organization table to plan atlas layout and animation frame rates
- 2.Determine tilemap tile size (16x16, 32x32, or 64x64) and set up background, terrain, props, and foreground layers
- 3.Select collision shapes (box, circle, capsule, polygon) based on your game objects
- 4.Choose a camera type (follow, look-ahead, multi-target, or room-based) matching your game genre
- 5.Implement genre-specific mechanics: for platformers add coyote time and jump buffering; for top-down configure movement direction and aiming
- 6.Test and avoid anti-patterns: use atlases instead of separate textures, simplify collision shapes, ensure smooth camera movement
Use cases
- Setting up sprite atlases to reduce draw calls in a 2D game engine
- Designing tilemap layers for a Metroidvania or platformer level
- Choosing appropriate collision shapes for character and object physics
- Implementing smooth camera follow with look-ahead for player anticipation
- Adding screen shake effects to impact moments like explosions or hits
- Game developers building 2D games
- Level designers working with tilemaps
- Programmers implementing physics and camera systems
- Anyone creating platformers or top-down games
2d-games FAQ
Typical range is 8-24 FPS. Lower rates work for pixel art; higher rates for smoother animations. Test with your art style.
Pick one approach and commit to it. Mixing both causes inconsistency. Physics-based is more flexible; pixel-perfect is more predictable for precise platformers.
Coyote time is a brief window (typically 4-6 frames) after leaving a platform where the player can still jump. It makes platformers feel more forgiving and responsive.
Always use atlases. They reduce draw calls, improve performance, and simplify batching. Combine multiple sprites into one texture sheet.
Use a follow camera type with smooth interpolation rather than snapping. Add look-ahead to anticipate player movement direction for better framing.
Full instructions (SKILL.md)
Source of truth, from sickn33/antigravity-awesome-skills.
name: 2d-games description: "2D game development principles. Sprites, tilemaps, physics, camera." risk: none source: community date_added: "2026-02-27"
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.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
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.
Related skills
More from sickn33/antigravity-awesome-skills and the wider catalog.
gcp-cloud-run
Specialized skill for building production-ready serverless
geo-fundamentals
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
git-pushing
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes (\"push this\", \"commit and push\"), mentions saving work to remote (\"save to github\", \"push to remote\"), or completes a feature and wants to share it.
github-workflow-automation
Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices.
graphql
GraphQL gives clients exactly the data they need - no more, no
hubspot-integration
Expert patterns for HubSpot CRM integration including OAuth