agentleFS
witnesstodarkwitnesstodark/mr-mak-workspace/.agents/skills/materials-to-game/SKILL.md

materials-to-game

Skill800 starsChanged 23 days agoMITView on GitHub

Create or apply material maps and bake a textured high-poly mesh onto a game mesh, with channel, UV and export checks.

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 supplied geometry when only a material change was requested.

    line 10

≈ “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

Materials and game bake-down

Identify the requested operation: generate material maps, retexture an existing mesh, or optimize a textured high-poly for a game. These are different tasks. Keep supplied geometry when only a material change was requested.

For fal material generation, discover the current Patina/material endpoint and read its schema using the fal module. The chosen material should be evaluated on the intended surface, not only as a preview tile. For mesh retexturing, inspect the chosen service's geometry/UV inputs separately.

For a high-to-low workflow:

  1. Preserve the textured high-poly source. Choose the target budget from the asset's role, silhouette, camera distance and engine constraints.
  2. Decimate or retopologize into a separate low-poly. Inspect thin parts, hard edges and the silhouette. A fixed face count is not suitable for every asset.
  3. Unwrap the low-poly, check texel density, seams, overlap and padding.
  4. Bake the required detail from source to target. Verify cage/ray distance, transforms and selected-to-active direction before trusting the bake.
  5. Identify base color, normal, roughness, metalness and any packed channels. Color maps and data maps need appropriate color-space settings. Check normal orientation in the target renderer; keep packed-channel conventions explicit.
  6. Export the low-poly with its maps. Reimport from another directory and check material links, scale, silhouette and texture resolution.

Example: a textured brass prop reduced for a distant game camera. Acceptance requires the same readable silhouette and a clean material at the gameplay distance; a smaller file alone is not sufficient. Preserve the source mesh. Dependencies: Blender or the chosen bake tool, supplied geometry/materials, and a provider account only for a requested remote generation.

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.