How do I install the 2d Games skill?

Run npx skillmds@latest add anhvu1107/2d-games in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 2d Games safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 2d Games?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 2d Games free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 2d Games?

anhvu1107 (@anhvu1107) published this skill. Their other Agent Skills are listed on their SkillMD profile.

2d Games by anhvu1107 — Agent Skill

Name: 2d Games
Author: anhvu1107

2d Games

ALWAYS use this when the user mentions 2d Games, asks to build, debug, review, document, automate, test, configure, migrate, or make decisions in this domain, or the task clearly depends on 2d Games; scope: 2D game development principles. Apply the bundled workflow, references, scripts, Senior Master standard, and Codex strict review gate before final output.

anhvu1107 4b17da4 8 files · 13.4 KB Updated Sep 17, 2026

File contents

2D Game Development

Selective Reading Rule

Start with:

references/senior-master-standard.md
references/usage-routing.md
references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

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.

---name: 2d-gamesdescription: ALWAYS use this when the user mentions 2d Games, asks to build, debug, review, document, automate, test, configure, migrate, or make decisions in this domain, or the task clearly depends on 2d Games; scope: 2D game development principles. Apply the bundled workflow, references, scripts, Senior Master standard, and Codex strict review gate before final output.---# 2D Game Development## Selective Reading RuleStart with:- `references/senior-master-standard.md`- `references/usage-routing.md`- `references/quality-checklist.md`Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.> 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 UseThis 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.

Frequently asked questions