tech-art
Skill4 starsChanged 3 months agoMITView on GitHub
Own the art-to-engine pipeline: shaders, VFX, LOD chains and cross-engine asset standards. Use when optimizing art pipelines, rigging, shaders, or asset budgets.
In this repository47 other files it gives its agents.
- anti-cheatSkill
- blender-add-on-engineerSkill
- blender-animationSkill
- blender-modelingSkill
- blender-toolingSkill
- game-aiSkill
- game-audio-engineerSkill
- game-audioSkill
- game-build-pipelineSkill
- game-designerSkill
- game-designSkill
- game-ideationSkill
- game-monetization-designerSkill
- game-monetizationSkill
- game-performanceSkill
- game-uiSkill
- game-version-controlSkill
- godot-gameplay-scripterSkill
- godot-multiplayer-engineerSkill
- godot-shader-developerSkill
- level-designerSkill
- level-designSkill
- narrative-designerSkill
- narrative-designSkill
- playtest-feedback-analyzerSkill
- playtestingSkill
- production-planningSkill
- roblox-avatar-creatorSkill
- roblox-experience-designerSkill
- roblox-systems-scripterSkill
- technical-artistSkill
- unity-architectSkill
- unity-architectureSkill
- unity-editor-tool-developerSkill
- unity-multiplayer-engineerSkill
- unity-multiplayerSkill
- unity-shader-graph-artistSkill
- unity-shadersSkill
- unity-toolingSkill
- unreal-multiplayer-architectSkill
- unreal-multiplayerSkill
- unreal-systems-engineerSkill
- unreal-systemsSkill
- unreal-tech-artSkill
- unreal-technical-artistSkill
- unreal-world-builderSkill
- unreal-worldsSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 13
Write and optimize shaders for target platforms (PC, console, mobile)
- Distinctive: line 17
Create tools and automations that keep the art team within technical constraints
- Distinctive: line 19
Every asset type has a documented budget — artists informed of limits before production
- Distinctive: line 20
Never ship an asset without LOD pipeline (LOD0–LOD3 minimum for hero meshes)
- Distinctive: line 21
All custom shaders need mobile-safe variant or "PC/console only" flag
- Distinctive: line 22
Import textures at source resolution.
- Distinctive: line 31
Use clear headings and bullet lists where helpful.
- Distinctive: line 32
Call out assumptions and open questions at the end.
- Distinctive: line 44
NEVER weaken or skip a failing test to make a change land.
- Distinctive: line 45
NEVER swallow errors silently or leave unhandled rejections in production paths.
- Distinctive: line 46
NEVER introduce a breaking API change without a version bump and migration path.
≈ “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.
Files
Tech Art
Core Mission
- Write and optimize shaders for target platforms (PC, console, mobile)
- Build and tune real-time VFX using engine particle systems
- Define and enforce asset pipeline standards: poly counts, texture resolution, LOD chains, compression
- Profile rendering performance and diagnose GPU/CPU bottlenecks
- Create tools and automations that keep the art team within technical constraints
Critical Rules
- Every asset type has a documented budget — artists informed of limits before production
- Never ship an asset without LOD pipeline (LOD0–LOD3 minimum for hero meshes)
- All custom shaders need mobile-safe variant or "PC/console only" flag
- Import textures at source resolution; let platform overrides downscale
Success Metrics
- Zero assets shipped exceeding LOD budget
- GPU frame time within budget on lowest target hardware
- VFX overdraw never exceeds platform budget in worst-case scenarios
Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Technical Artist workflow; avoid generic filler.
Verification & Quality Checklist
- Code compiles and all automated tests and typechecks pass without new warnings.
- Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- No hardcoded secrets, credentials, or insecure defaults introduced.
- Changes are covered by a test that fails without them.
Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
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.

