creating-sprites
Creating Sprites
Generate pixel-art game sprites via OpenAI's gpt-image-1.5 model with native transparent background support, then process them into game-ready assets with correct dimensions and proper anchoring.
Reference Files
| File | Read When |
|---|---|
references/sprite-sizes.md |
Choosing target size, generation size, crop mode, or fake pixel math for a sprite type |
references/prompt-guide.md |
Constructing or refining a generation prompt, choosing style keywords, or writing per-type prompts |
references/troubleshooting.md |
A generation fails, transparency check fails, style doesn't match, or API returns errors |
Prerequisites
OPENAI_API_KEY— an OpenAI API key- The generate script auto-loads from:
--api-keyflag →OPENAI_API_KEYenv var →.envfile in current directory
- The generate script auto-loads from:
- Python dependencies:
openaiandPillow(installed viarequirements.txtin the skill'sscripts/directory)
Script Paths
More from riccardogrin/skills
creating-skills
Guides creation of agent skills following best practices and the open format specification. Covers pattern selection, frontmatter, directory structure, reference files, validation, and iteration. Use when creating a new skill, updating SKILL.md, or asking "how to write a skill
16looping-tasks
Generates an autonomous implementation loop that executes tasks from a plan across Claude sessions, with periodic audit passes that inject follow-up tasks. Covers loop script, prompt design, and audit cadence. Use when setting up autonomous task execution or Ralph-style iterative workflows
16planning
Creates implementation-ready plans through discovery interviews, external research, and codebase analysis. Covers requirements, competitor research, architecture decisions, and change sequencing. Use when planning features, roadmaps, specs, or any work that needs discovery before coding
14listing-docs
Scans docs/ folder for markdown files with YAML front-matter and lists their summaries and read_when hints. Helps identify relevant documentation before coding. Use when starting a task, checking available docs, or asking "what docs exist
14enforcing-architecture
Sets up automated architecture enforcement via check scripts and hooks that catch layer violations on every file edit. Run after `/initializing-projects` for complex projects with 3+ distinct layers, or when no ARCHITECTURE.md exists and the codebase has clear architectural boundaries worth enforcing mechanically
14initializing-projects
Generates a minimal, self-maintaining CLAUDE.md for projects through auto-detection and developer interview. Covers project identity, do/don't rules, hooks, and self-maintenance. Use when starting a new project or adding Claude Code support to an existing one
13