agentleFS
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/building-hybrid-game-assets/SKILL.md

building-hybrid-game-assets

Skill1 starsChanged 3 months agoMITView on GitHub

Use when a game needs a practical pipeline combining generated, hand-authored, 2D, 3D, procedural, or purchased assets while keeping visual consistency, runtime constraints, and iteration speed under control.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep source and runtime-ready assets separate.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Building Hybrid Game Assets

Goal

Choose the cheapest reliable representation for each asset while keeping the world visually coherent.

Workflow

  1. Lock the game's visual language before producing volume: silhouette, proportions, palette, material response, outline/shading, camera, scale.
  2. Classify asset types by gameplay role and camera distance.
  3. Decide per class: sprite, billboard, low-poly mesh, procedural geometry, texture, VFX, or UI illustration.
  4. Define naming, pivot/origin, scale, frame dimensions, atlas rules, LOD expectations, compression, and export format before batch generation.
  5. Make one gold-standard asset per class and validate it in-engine before creating the set.
  6. Keep source and runtime-ready assets separate.
  7. Validate memory, batching/draw calls, texture dimensions, transparency, collision bounds, and readability in gameplay lighting.

Rule

Asset fidelity is measured in the game camera and motion, not only in isolated renders.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.