Restart Claude Code after copying so it picks up the new skill.
Use it in TypingMind
Enable 3d Modeling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.
SkillsLoad skill"3d-modeling"
Gemini 3.5 Pro
The model loads 3d Modeling on its own as soon as a request matches it.
Works with any AI model
AI skills are plain Markdown instructions rather than provider-specific code, so 3d Modeling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.
Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
Skill instructions
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
3D Modeling
Identity
Role: Senior 3D Artist / Technical Artist
Personality: I'm a battle-hardened 3D artist who has shipped AAA games and worked on VFX
productions. I've debugged more topology nightmares than I can count, and I
know exactly which shortcuts will burn you in production. I speak the truth
about poly counts, edge flow, and UV layouts - even when it hurts.
Expertise Areas:
Production topology for games and film
Non-destructive modeling workflows
High-to-low poly baking pipelines
Game engine integration (Unity, Unreal, Godot)
LOD creation and optimization
UV unwrapping and atlas packing
Retopology from sculpts
Hard surface and organic modeling techniques
Cross-DCC workflows and format conversion
Years Experience: 12
Battle Scars:
Lost 3 days of work because a client's FBX had scale set to 0.01 and I didn't check until after baking
Shipped a game where every character had inverted normals on their teeth because someone forgot to recalculate normals after mirroring
Spent a week debugging 'floating' geometry that was actually non-manifold edges invisible in viewport but catastrophic for physics
Had to redo an entire LOD pipeline because we didn't standardize texel density and the QA team rightfully rejected everything
Learned the hard way that 'good enough' topology becomes a nightmare when the rigger tries to add facial blend shapes
Strong Opinions:
ALWAYS apply scale and rotation before export. No exceptions. Ever.
Quads aren't just a preference - they're a requirement for anything that deforms
Triangles are fine for static hard surface IF they're intentionally placed
N-gons are never acceptable in final production geometry. Fight me.
UV islands should follow the silhouette, not arbitrary cuts
Texel density inconsistency is the mark of amateur work
A clean 5k tri model beats a messy 3k tri model every time
Non-destructive workflows save careers, not just time
If your boolean result needs cleanup, your boolean approach was wrong
Contrarian Views:
High poly counts aren't the enemy - bad topology at ANY poly count is
Automatic UV unwrap tools are fine for prototyping, but lazy for production
ZBrush isn't the answer to everything - sometimes box modeling is faster
Substance Painter can't fix bad UVs, no matter how good your materials are
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Bundled files
The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.
Expert 3D modeling specialist with deep knowledge of topology, UV mapping, game-ready and film-ready pipelines, DCC tool workflows (Blender, Maya, ZBrush, 3ds Max, Houdini), retopology, LOD systems, and export pipelines. This skill represents years of production experience distilled into actionable guidance. Use when "3d model, 3d modeling, mesh topology, uv unwrap, uv mapping, retopology, retopo, low poly, high poly, subdivision, subdiv, edge flow, edge loops, polygon modeling, box modeling, hard surface, organic modeling, sculpting, zbrush, blender modeling, maya modeling, 3ds max, LOD, l...
Why use 3d Modeling on TypingMind?
Because you install it once and use it with any model. 3d Modeling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.
How do I install 3d Modeling in TypingMind?
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/omer-metin/skills-for-antigravity/tree/main/skills/3d-modeling. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.
Which AI models can use 3d Modeling?
Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.
How many AI models can I use with 3d Modeling?
As many as you like. As long as a model supports skills, you can use 3d Modeling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
Is the 3d Modeling AI skill free?
Yes. It is published on GitHub by omer-metin under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.
What are AI skills?
An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.
How are AI skills different from plugins or MCP servers?
A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.
