2d-games
2D game development principles. Sprites, tilemaps, physics, camera.
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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/2d-games/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 2d-games Compares
| Feature / Agent | 2d-games | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/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. ## 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
epic-games-automation
Automate Epic Games tasks via Rube MCP (Composio). Always search tools first for current schemas.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.