Hire an AI Unity editor tool developer

Everything it can hand back

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

• The kind of tool to build and why that kind fits
• A spec for what it checks or does, and what the user sees
• The rules it must follow, such as Undo and editor-only code
• A C# outline of the main tool
• A test list and a way to try it with the real user first

How it does the job well

• Do not promise time saved, adoption or speed. Say how to measure them.
• Use a Unity method name only if you are sure it exists. If not, write "confirm in the Unity docs".
• Never claim code compiles or works. You have not run it.
• Tools that change many assets at once must plan a dry run first, so the user can see the changes before they happen.
• 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 import settings by hand on every new texture or model.

• The job. The manual task, who does it, how often, and what goes wrong today.
• Tool choice. Which kind of editor tool fits, and why the others do not.
• Spec. What the tool checks or changes, what the user sees and the message when it acts.
• Rules it must follow. Editor-only code, Undo, progress bars and settings that are safe to apply twice.
• Code outline. The main class and key Unity calls, marked untested.
• Test list. Tests to run in Unity, each with an expected result.

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.

Capabilities

• Find the job. It names the repeated manual job and who does it, because the tool is judged by that person.
• Pick the tool kind. It chooses between an editor window, a drawer, an import rule, a menu item or a build check, and says why.
• Write the spec. It says what the tool checks or changes, what the user sees and what message appears when it acts.
• Apply the rules. It adds editor-only code, Undo, progress bars on slow work and warnings when a rule changes a setting.
• Outline the code. It sketches the main class and the Unity calls it needs, marked untested.
• Plan the trial. It plans a first version, a try-out with the real user and a build check wired in last.

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 unity-editor-tool-developer 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/unity-editor-tool-developer/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 job people do by hand, and how often
• Who will use the tool, such as an artist, a designer or a build engineer
• Your Unity version
• The rules to enforce, such as naming, texture size or required components (optional)
• Existing editor scripts, if any (optional)

Helpful context (optional)

• A screenshot of the manual job or the Unity panel involved.
• The rules your team follows today, such as a naming guide.

Tools and access

• Claude, ChatGPT or Gemini: Any of them can plan the tool and outline the C#. One that can browse can check the current Unity docs.

Functions and deliverables

• Unity editor tool developer: Plan a custom Unity Editor tool, such as an asset checker, inspector drawer or import rule, with Undo support and a build check.
  • The kind of tool to build and why that kind fits
  • A spec for what it checks or does, and what the user sees
  • The rules it must follow, such as Undo and editor-only code
  • A C# outline of the main tool
  • A test list and a way to try it with the real user first
  Source: Michael Sitarzewski and Agency Agents contributors.
• AI tool picker: Describe the job you want done. Get the kind of AI tool that fits, tools to try first and a backup.
  • The kind of tool that fits the job, and why
  • One or two tools to try first, and a backup
  • What to check on each tool's own site before you commit
  • A first small task to try, so you learn quickly if it fits
• UI detail and code performance editor: Choose one interface detail or slow function. Compare checked attempts within a fixed budget and keep the best supported version, including the original.
  • The best checked version of your target
  • A short note on each attempt and how it was tested
  • Before and after evidence
  • A clear statement of whether the goal was met
  Source: sickn33.
• Import and export paperwork checker: Describe your goods and route. Check official tariff and customs sources, then list supported options and open questions.
  • A supported tariff code or the facts still needed
  • Duty options to check
  • A document list with sources and check dates
  • Trade term suggestions
  • Common mistakes to avoid
  Source: sickn33.
• 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

Tasks you can use it for

• Your artists fix the same import settings by hand on every new texture or model.
• Broken assets, such as oversized textures or wrong names, reach testing before anyone notices.
• Your designers struggle to edit a field in the Inspector, and a custom drawer would help.
• You want the build to stop automatically when a project rule is broken.

Limits to check before starting

• You want code that runs inside the game for players. Use the Unity software architect.
• You want a shader or look for materials. Use the Unity Shader Graph artist.
• You want a general developer tool outside Unity. Use the Developer tools engineer.
• Your team only needs a written checklist. Tooling costs more than a list does.

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 and add it to your AI as a skill. If you cannot, paste SKILL.md and then references/source-agent.md into a new chat.
• Describe the manual job, who does it and how often. Add your Unity version. Say MISSING for anything you do not know.
• Say "Pick the right tool kind, then give me the spec." Ask for the code outline only after you agree on the spec.
• Read the tool choice first. If it picks a window but you wanted an automatic rule, say so and ask again.
• Build the first version in Unity. Let the real user try it before you polish it. Write down where they get confused.
• Paste what you learned back and ask for the next version.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/unity-editor-tool-developer 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.