DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find z-fighting and floating parts, then export to Roblox with Blender Skills

Have an agent check a model for z-fighting, floating parts and bad normals before exporting it to Roblox.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA Roblox creator who wants to catch geometry problems before a model goes into the game.

The problemZ-fighting, floating parts and bad normals are easy to miss in the viewport and can show up only after export.

The outcomeA QA report on the model and a Roblox-ready export, produced after the asset QA skill has run.

What you need first

  • Blender 5.2 or newer installed
  • git to clone the repository
  • An AI coding agent such as Claude Code, Codex, Gemini CLI or Cursor
  • Optional: a Blender MCP server so agents can work in your open Blender session

Steps

  1. Clone the repository: git clone https://github.com/EL4CTEO/blender-skills
  2. Install the skills: ./blender-skills/install/install.sh (macOS / Linux) or .\blender-skills\install\install.ps1 (Windows)
  3. Ask the agent to run the asset QA skill on the model and list any z-fighting, floating parts, bad normals or weights it finds.
  4. Ask the agent to fix the listed issues and re-run the check.
  5. Ask the agent to export the cleaned model for Roblox with the export pipelines skill.

Prompt for your agent

Using the blender-skills repo, check <model file> for z-fighting, floating parts, bad normals and bad weights, fix what it finds, then export it for Roblox. Expect a QA list before and after the fixes and the exported file. Verify that the second QA pass reports no remaining issues before the export runs.

Caveat. The QA skill reports the defects the README names, but it does not claim to catch every problem a Roblox import could raise, so test the upload in Roblox Studio.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page