forge-texture
Skill2 starsChanged 5 months agoNo licenceView on GitHub
Forge suite — texture baking and procedural texture authoring (the lookdev texture layer). Bakes normal maps, ambient occlusion, curvature, displacement/height, and combined PBR map sets from a high-poly source onto a low-poly mesh with cage support — headlessly via Blender + Cycles. Also builds procedural shader networks (Noise/Voronoi/Wave/Gradient nodes) and bakes them to tileable PNGs, generates PBR map sets from a single albedo image, downloads CC0 textures from PolyHaven or ambientCG, and compresses finals to KTX2 or WebP. Use whenever asked to: bake textures, bake normals, bake AO, high-poly to low-poly bake, cage bake, transfer detail from sculpt, bake curvature map, bake displacement or height map, bake PBR maps, build a procedural material and bake it, convert height to normal, make a tileable texture, compress textures to KTX2, flip normal map green channel for Unreal/DirectX, download a free PBR texture, or generate a seamless texture. HEADLESS-ONLY: driven from code, output verified by reading a PNG. Part of the Forge suite.
In this repository38 other files it gives its agents.
- atelier-componentsSkill
- atelier-copySkill
- atelier-dataSkill
- atelier-datavizSkill
- atelier-directionSkill
- atelier-foundationsSkill
- atelier-hardenSkill
- atelier-layoutSkill
- atelier-motionSkill
- atelier-perf-a11ySkill
- atelier-redesignSkill
- atelier-reviewSkill
- atelier-scrollSkill
- atelierSkill
- atelier-typographySkill
- atelier-uxSkill
- atelier-webglSkill
- codex-imagegenSkill
- codex-imagegen-tasteSkill
- forge-animateSkill
- forge-briefSkill
- forge-dataSkill
- forge-exportSkill
- forge-intakeSkill
- forge-lightSkill
- forge-materialSkill
- forge-modelSkill
- forge-optimizeSkill
- forge-parametricSkill
- forge-proceduralSkill
- forge-renderSkill
- forge-rigSkill
- forge-simSkill
- forgeSkill
- forge-standardsSkill
- forge-topologySkill
- forge-uvSkill
- forge-validateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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
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.

