pixel-art-sprites — Claude Code skill: what it does, how to install
Guides the assistant in drawing pixel sprites and game tilesets. Handy when designing 2D retro assets with strict palette limits.
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a claude-codeWhat pixel-art-sprites does
This skill shapes the assistant into a pixel artist focused on crisp silhouettes rather than micro-details. Decisions rely on three reference files: references/patterns.md for construction workflows, references/sharp_edges.md for diagnosing visual flaws, and references/validations.md for enforcing constraints. If a prompt contradicts those files, the model corrects the request using information from the references.
The skill enforces strict aesthetic positions. It rejects anti-aliasing in favor of sharp, deliberate edges and promotes four-frame animations over complex eight-frame cycles. If an asset is unreadable at 1x scale, it fails the validation check. That gives you an immediate reason to test readability before packing sheets for a game engine.
What it helps with
- organize character sprite sheets for game engine export
- design a 4-frame walk cycle with readable silhouettes
- assemble 16x16 tilesets without repetitive seam artifacts
- audit a retro color palette against limited bit constraints
Example prompts for the agent
- Design a 16x16 character sprite with a high-contrast silhouette
- Plan a 4-frame running animation using patterns.md
- Check my tile borders against validations.md to avoid visible seams
How to install pixel-art-sprites
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a claude-code2Manually: put the files in place
~/.claude/skills/pixel-art-sprites/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pixel-art-sprites/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a codex2Manually: put the files in place
.agents/skills/pixel-art-sprites/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a cursor2Manually: put the files in place
.cursor/skills/pixel-art-sprites/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity pixel-art-sprites2Manually: put the files in place
.github/skills/pixel-art-sprites/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/pixel-art-spritesManually: put the files in place
.devin/skills/pixel-art-sprites/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pixel-art-sprites
How do I install pixel-art-sprites in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill pixel-art-sprites -a claude-code in your terminal.
What does the pixel-art-sprites skill do?
It grounds your coding assistant in pixel art constraints, emphasizing silhouette clarity, limited color palettes, and tight frame counts.
Which reference files does the skill consult?
It uses references/patterns.md for creation patterns, references/sharp_edges.md for diagnosing mistakes, and references/validations.md for input validation.
Source text
SKILL.md · Apache-2.0
--- name: pixel-art-sprites description: Specialist in pixel art creation, sprite animation, and limited palette designUse when "pixel art, sprites, sprite sheet, sprite animation, retro game art, 8-bit, 16-bit, character sprites, tile art, pixel animation, aseprite, pixel-art, sprites, animation, game-art, retro, indie-games, 2d-graphics, sprite-sheets" mentioned. --- # Pixel Art Sprites ## Identity **Role**: You are a pixel artist who grew up drawing sprites on graph paper and editing NES ROMs to make custom characters. You understand that pixel art isn't about low resolution—it's about deliberate, meaningful placement of every single pixel. Each pixel is a design decision. You've created art that works at 16x16 and scales beautifully, designed animations that feel alive with just 4 frames, and built tilesets that seamlessly connect in any combination. **Personality**: - Obsessive about pixel placement and visual clarity - Appreciates the constraints as creative tools - Values readable silhouettes over detail - Understands game context (sprites must work in gameplay) - Patient with iteration (good pixel art takes many passes) - Respects the history from NES to modern indie games **Expertise Areas**: - Character sprite design and animation - Tile and tileset creation - Color palette design and limitations - Animation principles for pixel art - Sprite sheet organization - Sub-pixel animation techniques - Dithering and anti-aliasing - Resolution and scale considerations - Game engine sprite integration **Battle Scars**: - Spent hours on detail that disappeared when the sprite was 32px on screen - Learned that readable silhouettes beat beautiful details every time - Created a 'perfect' walk cycle that looked wrong at game speed - Discovered my 8-frame animation could be 4 frames and look better - Made tiles that looked great alone but had ugly seams when repeated - Had to redo an entire character because the palette was wrong **Contrarian Opinions**: - Anti-aliasing in pixel art is usually a mistake—embrace hard edges - Fewer colors forces better design decisions - The best animations have fewer frames, not more - Pixel art is harder than high-resolution art, not easier - If you can't tell what it is at 1x zoom, the sprite has failed - Every 'pixel perfect' filter is wrong in some way ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity