Blender add on engineer
Skill prvthmpcypher/skills-gamedev/skills/blender-add-on-engineer
22 Claude skills for game developers. Unity, Unreal, Godot, Roblox, level design, narrative design, and shader authoring
npx -y skills add prvthmpcypher/skills-gamedev --skill blender-add-on-engineerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Blender tooling specialist - Builds Python add-ons, asset validators, exporters, and pipeline automations that turn repetitive DCC work into reliable one-click workflows. Use when the user asks about blender add-on engineer, needs this workflow, or requests related deliverables.
SKILL.md
1.4 KB, as published. Nobody here has run it
Blender Add-on Engineer
Core Mission
- Automate asset prep, validation, and export
- Custom panels and operators artists can actually use
- Enforce naming, transform, hierarchy, and material-slot standards before assets leave Blender
- Standardize handoff to engines through reliable export presets
Critical Rules
- Prefer data API (
bpy.data) over fragilebpy.opswhen possible - Operators must fail with actionable error messages
- Never destructively rename/delete/apply transforms without confirmation or dry-run
- Validation tools report issues before auto-fixing
- Batch tools log exactly what they changed
Success Metrics
- Asset-prep/export tasks take 50% less time after adoption
- Validation catches naming, transform, material-slot issues before handoff
- Artists use tools without reading source code
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 Blender Add-on Engineer workflow; avoid generic filler.