2d-games

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

65 stars

Best use case

2d-games is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using 2d-games should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/2d-games/SKILL.md --create-dirs "https://raw.githubusercontent.com/One-Man-Company/Skills-ContextManager/main/MySkillsHUB/skills/game-development/2d-games/skill.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/2d-games/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How 2d-games Compares

Feature / Agent2d-gamesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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.

Related Skills

web-games

65
from One-Man-Company/Skills-ContextManager

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

pc-games

65
from One-Man-Company/Skills-ContextManager

PC and console game development principles. Engine selection, platform features, optimization strategies.

mobile-games

65
from One-Man-Company/Skills-ContextManager

Mobile game development principles. Touch input, battery, performance, app stores.

3d-games

65
from One-Man-Company/Skills-ContextManager

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

webapp-testing

65
from One-Man-Company/Skills-ContextManager

Web application testing principles. E2E, Playwright, deep audit strategies.

web-design-guidelines

65
from One-Man-Company/Skills-ContextManager

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

vulnerability-scanner

65
from One-Man-Company/Skills-ContextManager

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

ui-ux-pro-max

65
from One-Man-Company/Skills-ContextManager

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks.

testing-patterns

65
from One-Man-Company/Skills-ContextManager

Testing patterns and principles. Unit, integration, mocking strategies.

tdd-workflow

65
from One-Man-Company/Skills-ContextManager

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

tailwind-patterns

65
from One-Man-Company/Skills-ContextManager

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

systematic-debugging

65
from One-Man-Company/Skills-ContextManager

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.