{
 "schema": "aiblocks-page/1",
 "id": "agency-blender-addon-engineer",
 "type": "agent",
 "name": "Blender add-on developer",
 "summary": "Turn a repeated Blender chore into a Blender add-on plan and starter Python code. Check asset names, scale and materials before export.",
 "headline": "Blender add-on developer",
 "subhead": "Describe the chore your artists repeat in Blender, your Blender version and where assets go next. It plans the smallest useful add-on, writes starter Python code for it, and gives you a safe way to test it on a copy of your scene.",
 "job": {
  "id": "build-software",
  "name": "Build and ship software"
 },
 "level": "intermediate",
 "thinking": "high",
 "tested": true,
 "updated": "2026-11-03",
 "first_published": "2026-10-26",
 "inputs": [
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  },
  {
   "type": "codebase",
   "required": false,
   "label": "Codebase",
   "what": "a project's code, in a folder or repo the AI can open"
  }
 ],
 "outputs": [
  {
   "type": "code_change",
   "required": true,
   "label": "Code change",
   "what": "a change to the code, with what it fixes and how it was checked"
  }
 ],
 "you_give": [
  "The chore, step by step, as an artist does it by hand today",
  "Your Blender version, such as 4.2, and where the assets go next, such as Unity, Unreal or glTF",
  "Your naming rules and the mistakes you see most often",
  "An existing add-on file or script (optional)",
  "A sample of an asset that breaks the rules, described or as a list of its object names (optional)"
 ],
 "you_get": [
  "A plan for the smallest useful tool, and what it will check or fix",
  "Starter Python code for the add-on, in files you can copy, with a panel and operators",
  "A list of the rules the tool enforces, and which are check-only and which can auto-fix",
  "A sample validation report layout, with object, rule, details and suggested fix",
  "Steps to install the add-on and test it on a copy of a scene",
  "A short list of things to check before you give it to your team"
 ],
 "use_when": [
  "Your artists fix the same naming, scale or material mistakes before every export.",
  "An asset reached Unity, Unreal or glTF with a wrong scale or a missing material.",
  "You want one button that checks a scene and then exports it with fixed settings.",
  "You want a panel that shows rules your team agreed, so no one has to remember them."
 ],
 "skip_when": [
  "You want to learn to model, sculpt or texture. Use Blender's own manual and tutorials.",
  "You need an editor tool for Unity instead. Use the Unity editor tool developer.",
  "You need materials and effects set up inside Unreal. Use the Unreal technical artist.",
  "You want a finished add-on you can trust without testing. Any add-on must be tested by you in Blender, on a copy of your scene first.",
  "You want a paid or commercial add-on checked for licence terms. Ask a lawyer."
 ],
 "output_sample": {
  "input": [
   "The chore your artists repeat, step by step",
   "Your Blender version and the engine or format the assets go to",
   "Your naming rules and the mistakes you see most often",
   "An existing add-on or script (optional)"
  ],
  "prerequisites": [
   "An AI that can write Python, such as Claude, ChatGPT or Gemini",
   "Blender installed, and a copy of a scene to test on"
  ],
  "output": [
   {
    "name": "Tool plan",
    "contains": "The smallest useful add-on, the rules it checks, and what is check-only or may auto-fix."
   },
   {
    "name": "Add-on code files",
    "contains": "Starter Python for settings, operators and a panel, marked as not tested."
   },
   {
    "name": "Validation report layout",
    "contains": "A table of object, rule, details and suggested fix for each problem found."
   },
   {
    "name": "Install and test steps",
    "contains": "How to add the file in Blender and try it on a copy of a messy scene."
   },
   {
    "name": "Checks before the team uses it",
    "contains": "What to confirm on real scenes before others rely on the add-on."
   },
   {
    "name": "Checks not run",
    "contains": "What the AI could not do, such as running the code in Blender."
   }
  ]
 },
 "output_shape": "BRIEF AND ASSUMPTIONS\n  <chore> | Blender version <x> | destination <Unity, Unreal, glTF or other> | ASSUMED: <list> | MISSING: <list>\n\nTOOL PLAN\n  smallest useful tool <checker, exporter, cleanup or panel> | rules enforced <list> | check-only <list> | may auto-fix <list, each needing a dry run or a yes>\n\nFILES\n  <file name> | what it holds <settings, operators, panel, export>\n  <code, one block per file, marked NOT TESTED>\n\nVALIDATION REPORT LAYOUT\n  <object> | <rule> | <details> | <suggested fix> | severity <error or warning>\n\nINSTALL AND TEST STEPS\n  <numbered steps in Blender> | test on a copy of a messy scene | what a pass looks like\n\nCHECKS BEFORE THE TEAM USES IT\n  <item> | <how to check>\n\nCHECKS NOT RUN\n  <each thing the AI could not run, such as running the add-on in Blender>",
 "how_to_use": [
  "Download the pack from this page and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.",
  "Write a short brief. Include your Blender version, the chore step by step, the destination such as Unity or glTF, and your naming rules.",
  "Your AI asks once for anything missing. Anything still unknown is marked as an assumption you can change.",
  "Read the plan before the code. Check the rules are the ones your team really uses, and that nothing is changed without a dry run or your yes.",
  "Make a copy of a messy scene. Install the add-on from a file in Blender's preferences, run the checker and read the report.",
  "Paste any error from Blender's system console back into the chat and ask for a fix. Only give it to your team once it works on real scenes.",
  "Next, take the checker's report to a team review. Add each new mistake you find to the rule list and run it again on the copy."
 ],
 "checks": [
  "The result addresses your actual task and cites the evidence used.",
  "Examples, role-play experience and targets are kept separate from verified results.",
  "Claims of tests, memory, tool access or completed actions match what actually happened."
 ],
 "next": [
  {
   "name": "Simple code coach",
   "url": "https://useaiblocks.com/skills/simple-code-coach",
   "why": "Build it"
  }
 ],
 "source": {
  "by": "Michael Sitarzewski and Agency Agents contributors",
  "repo": "msitarzewski/agency-agents",
  "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/game-development/blender/blender-addon-engineer.md",
  "licence": "MIT",
  "original_name": "Blender Add-on Engineer",
  "commit": "b37b5bb33b78f2c1d6567d98e25ca818e3259219"
 },
 "credits": [
  {
   "title": "Blender Add-on Engineer",
   "by": "Michael Sitarzewski and Agency Agents contributors",
   "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/game-development/blender/blender-addon-engineer.md",
   "used": "Original agent profile, preserved in references/source-agent.md; AI Blocks adds setup and review instructions."
  }
 ],
 "files": [
  "LICENSE",
  "references/source-agent.md",
  "SETUP.md",
  "source.json"
 ],
 "links": {
  "page": "https://useaiblocks.com/agents/agency-blender-addon-engineer",
  "markdown": "https://useaiblocks.com/agents/agency-blender-addon-engineer.md",
  "json": "https://useaiblocks.com/agents/agency-blender-addon-engineer.json",
  "instructions": "https://useaiblocks.com/skills/agency-blender-addon-engineer/SKILL.md",
  "download": "https://useaiblocks.com/skills/agency-blender-addon-engineer.zip",
  "api_item": "https://useaiblocks.com/api/v1/items/agency-blender-addon-engineer",
  "api_document": "https://useaiblocks.com/api/v1/documents/agent/agency-blender-addon-engineer",
  "mcp": "https://useaiblocks.com/mcp"
 }
}