Automated summary
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
How this analysis is madeExamples
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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/2d-game-development-mrwakbmc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/2d-game-development-mrwakbmc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/2d-game-development-mrwakbmc/download' --output '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md.part' && mv '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md.part' '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md' && test -s '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/2d-games' && cp -R '.skill-downloads/2d-game-development-mrwakbmc' '.claude/skills/2d-games'Cursor
test -f '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md' && test -s '.skill-downloads/2d-game-development-mrwakbmc/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/2d-games' && cp -R '.skill-downloads/2d-game-development-mrwakbmc' '.cursor/skills/2d-games'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/2d-game-development-mrwakbmc'openskills read '2d-game-development-mrwakbmc'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/2d-game-development-mrwakbmc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.