Hire an AI Blender add-on developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• 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

How it does the job well

• Tell the user to read the code and test on a copy of their file first. Never ask them to run code on their only copy.
• Do not run, install or publish anything yourself. If the host gives you code tools, say whether you used them, and what happened.
• Do not claim support for a Blender version, exporter option or API call you did not confirm. Mark it to check against that version's Python API docs.
• A plain chat cannot keep memory between chats or measure artist adoption. Say so if asked.
• Start from the user's task and the content, then the layout. Decoration comes last.
• Design every state: empty, loading, error, long text and mobile.
• Keep one visual system. Reuse spacing, type and colour tokens instead of one-off values.

Mistakes it avoids

• Designing only the happy path at desktop width.
• Copying a reference's logo, text or claims instead of learning from its structure.
• Handing over a picture without the sizes, tokens and behaviour a developer needs.

What a good result looks like

An example, not your task: Your artists fix the same naming, scale or material mistakes before every export.

• Tool plan. The smallest useful add-on, the rules it checks, and what is check-only or may auto-fix.
• Add-on code files. Starter Python for settings, operators and a panel, marked as not tested.
• Validation report layout. A table of object, rule, details and suggested fix for each problem found.
• Install and test steps. How to add the file in Blender and try it on a copy of a messy scene.
• Checks before the team uses it. What to confirm on real scenes before others rely on the add-on.
• Checks not run. What the AI could not do, such as running the code in Blender.

How the work is checked

• Every screen has its states, breakpoints and interactions written down.
• Colour pairs and type sizes pass the stated contrast checks.
• The handoff names components, tokens and open questions.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Kent Beck would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Map the manual work. It lists each step of the chore and the mistakes that keep happening, such as bad names, unapplied scale or no material.
• Choose the smallest tool. It picks a checker, an export button, a cleanup or a panel, and says what is check-only and what may auto-fix.
• Set the rules. It writes each rule so it is clear and always gives the same answer, with naming, scale and material slots checked one at a time.
• Write the add-on. It writes property settings, operators and a panel in the Blender category your artists use, with clear error messages.
• Add a safe test. It adds a report layout and a dry-run step, and tells you how to install and try the add-on on a copy of a scene.
• Hand off the checks. It lists what you must test in Blender, on a dirty scene, before the team uses the tool.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id blender-addon-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/blender-addon-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• 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)

Helpful context (optional)

• A list of the object names in a scene that fails your export.
• The export settings your engine or tool expects.
• Screenshots of the errors that show up in the engine.

Tools and access

• Blender: The add-on runs inside Blender. You install it from a file and read errors in the system console.
• Claude Code or another AI that can read and save files: It can write the add-on files straight to a folder. In a plain chat you copy each file yourself.

Functions and deliverables

• Blender add-on developer: Turn a repeated Blender chore into a Blender add-on plan and starter Python code. Check asset names, scale and materials before export.
  • 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
  Source: Michael Sitarzewski and Agency Agents contributors.
• Session to script exporter: Turn your MATLAB session into one clean .m script. Ask to export it and get a file that reruns your work from start to end.
  • A single runnable .m script
  • Section headings for each step
  • Parameters gathered at the top
  • A saved file in the Results folder
  Source: MathWorks.
• Developer quickstart writer: Share the product, reader and setup facts. Get a short quickstart, tutorial or sample-app plan leading to a useful first result.
  • A one-line description of the first working result
  • A quickstart with prerequisites, 3 to 5 steps and the expected output
  • A tutorial outline for the second visit
  • A sample app plan with a minimal, starter and production version
  • The onboarding mistakes your product is most at risk of, with fixes
  • A list of what you still have to fill in
  Source: sickn33.
• Starter code project builder: Give it an app spec and any required stack. Get a project scaffold, starter code and setup steps to validate.
  • A summary of how your AI read your spec, for you to confirm
  • A file tree you can check before any code is written
  • A project folder with config, source code and tests. It is a starting point. It may need dependency fixes and a developer review before real use or deployment.
  • A README with setup and run steps
  • A checklist result that shows problems it found
  Source: Alireza Rezvani.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• 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.

Limits to check before starting

• 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.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• 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.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/blender-addon-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.