gamedev-skills/awesome-gamedev-agent-skills / skills/disciplines/create-game-assets
create-game-assets
VerifiedPlans, generates or sources, and validates consistent game art: style guides, sprites, pixel art, tilesets, icons and textures, with QA and licence records. Use when making or AI-generating game art, fixing fake transparency, or checking Steam AI disclosure. Not for engine import (`godot-tilemap`, `godot-animation`, `unity-tilemap-2d`), UI layout (`game-ui-ux`) or sound (`audio-design`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| agents/openai.yaml | config | 231 B |
| assets/art-direction-brief.md | markdown | 858 B |
| assets/asset-manifest.json | config | 969 B |
| references/art-direction.md | markdown | 3.8 KB |
| references/provenance.md | markdown | 2.5 KB |
| references/raster-pipeline.md | markdown | 4.1 KB |
| references/three-d-pipeline.md | markdown | 3.1 KB |
| scripts/asset_report.pyexecutable | script | 5.3 KB |
| scripts/build_preview_sheet.pyexecutable | script | 3.3 KB |
| scripts/requirements.txt | manifest | 15 B |
references/provenance.md
View on GitHub# Asset rights and provenance
Use this reference for generated, purchased, commissioned, open, or remixed assets. This is a
production recordkeeping workflow, not legal advice.
## Record per shipped asset
- stable asset ID and repository path
- creator/source URL or vendor order
- acquisition or generation date
- source tool/model/version when generated
- original prompt/reference IDs when available
- license name/version and a saved copy or link to the terms
- attribution text and placement requirements
- whether commercial use, modification, redistribution, or AI training is restricted
- edits, derivatives, and the person/tool responsible
- approval status and reviewer
The bundled `assets/asset-manifest.json` has fields for these records. Keep proof of purchase and
license snapshots outside a public repository when they contain personal or account data.
## Decision rules
1. Do not treat “free,” “royalty-free,” search-engine-visible, or model-generated as a license.
2. Verify terms at the original source, not a repost or aggregator preview.
3. Keep attribution through atlas packing, renaming, conversion, and derivative edits.
4. Check whether a marketplace license permits redistribution of raw source files; shipping a game
and publishing editable source assets can have different permissions.
5. Do not request direct imitation of a living artist. Describe visual properties or use references
the project has permission to edit.
6. Preserve content credentials/provenance metadata where the file pipeline supports it. If
optimization strips metadata, retain the corresponding manifest record.
7. Review each store/platform's current disclosure rules before submission; rules change faster
than this skill. Steam's Content Survey has a required generative-AI section that separates
content made during development from content generated while the game runs. Record which
assets were generated so that section can be answered from the manifest, not from memory.
## Useful primary references
- [Creative Commons license chooser](https://creativecommons.org/chooser/)
- [SPDX license list](https://spdx.org/licenses/)
- [C2PA (Content Credentials) specifications](https://spec.c2pa.org/specifications/)
- [OpenAI content provenance](https://openai.com/index/advancing-content-provenance/)
- [Steamworks Content Survey, including the generative AI section](https://partner.steamgames.com/doc/gettingstarted/contentsurvey)
When terms are unclear or the release is commercially important, flag the ambiguity for a human
rights review rather than guessing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |