Hire an AI XR cockpit interaction designer

Everything it can hand back

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

• A control list with type, input method, feedback and movement limits for each
• A layout plan that groups controls into reach zones by how often they are used
• A feedback guide for light, sound and motion on each control
• A comfort check list for a seated view
• A usability test plan with tasks to try and what to measure

How it does the job well

• You cannot wear a headset or run a test with users. Say Not run for any check you could not do. Never say a check passed when you did not run it.
• The profile gives no measured reach distances, control sizes or motion sickness limits. Never state one as fact. If you give a figure, label it "assumption, check your headset maker's guidance and test with users".
• A layout sketch in A-Frame or Three.js is an untested draft. Say so above the code. Do not claim it runs.
• Keep general XR menus and HUDs out of scope. Point to the XR Interface Architect agent.
• Do not invent a fact about the user's project. If a figure is not from the user, label it as an assumption.
• 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.

Mistakes it avoids

• Free-floating motion of the user's viewpoint.
• Stating a comfort or reach limit as a rule with no source.
• Designing general menus or panels. That belongs to the interface agent.
• 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: You are building a flight, driving, space or control-room trainer for a headset.

• Control list. Each control with its type, how the user works it, movement limit and feedback.
• Layout plan. Reach zones by how often each control is used, and the fixed view anchor.
• Feedback guide. A light, sound and moment of firing for every control.
• Comfort checks. Seated comfort items marked Pass, Risk or Can't tell, with the reason.
• Usability test plan. Tasks for real users, what to measure and what counts as trouble.
• Prototype notes. An optional A-Frame or Three.js layout sketch, marked untested.

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 Don Norman and Jakob Nielsen would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Fix the brief. It confirms the station, the tasks, the headset, the inputs and seated or standing. Gaps are asked once, then marked MISSING.
• List the controls. Each control gets a type, an input method and a limit on how it moves, so nothing floats free.
• Place the controls. It groups them by how often they are used, and keeps the seat and view as a fixed anchor.
• Write the feedback. Each control gets a visual cue, a sound and a moment when it fires.
• Check comfort. It runs a seated comfort check list on the plan and marks each item Pass, Risk or Can't tell.
• Plan the tests. It lists tasks for real users, what to measure and what counts as trouble.

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 xr-cockpit-interaction-specialist 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/xr-cockpit-interaction-specialist/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 vehicle or station, such as a plane cockpit or a control room, and the tasks the user does in it
• Your headset and how users act: controllers, hand tracking, voice, gaze or physical props
• Seated or standing, and the play space you have
• The controls you think you need, as a list (optional)
• Your tools, such as A-Frame, Three.js or Unity (optional)

Helpful context (optional)

• Photos or a diagram of the real cockpit
• Your headset maker's comfort guidance
• A written list of the tasks in order

Tools and access

• Claude, ChatGPT or Gemini: Any chat AI can write the control list and layout. Pick one that can read photos of a real cockpit you want to copy.

Functions and deliverables

• XR cockpit interaction designer: Plan the controls and layout of a seated XR cockpit: reach zones, input methods, feedback and comfort checks, from your task list.
  • A control list with type, input method, feedback and movement limits for each
  • A layout plan that groups controls into reach zones by how often they are used
  • A feedback guide for light, sound and motion on each control
  • A comfort check list for a seated view
  • A usability test plan with tasks to try and what to measure
  Source: Michael Sitarzewski and Agency Agents contributors.
• Interface interaction details designer: Find what is missing in the small moments of your screen, like a toggle or loading state. Get a score out of ten and a ranked list of fixes.
  • Trigger, rules, feedback and loop notes for each moment
  • A score out of ten against eight checks
  • A short list of fixes in priority order
  • Ideas for motion and feedback
  Source: Wondel.ai.
• Nature-based classroom layout planner: Describe your room, goal, budget and limits. Get a staged plan for light, layout and natural materials. Design guidance, not medical advice.
  • A staged redesign plan
  • Light and layout changes
  • Plant and natural material ideas
  • Options that fit your budget
  Source: Gareth Manning.
• Warehouse layout planner: Give it your products, volumes and building size. Get zones, aisle layout, storage type and space needed.
  • A zone plan for receiving, storage, picking, packing and shipping
  • A storage type choice with the reason for it
  • Pallet positions and total floor space needed
  • Dock door counts and aisle sizes
  • A list of open questions for your landlord or supplier
  Source: Kishor Kukreja.
• 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
• Don Norman: Find why a product, form or service is hard to use through Don Norman’s public approach. Check cues, controls, feedback and recovery from mistakes.
  • Your problem worked on the way Don Norman would: their questions, their method, their push-back
  • The answer or the work, in Don Norman's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jakob Nielsen: Review a website, app or form through Jakob Nielsen’s recorded approach. Find likely usability problems and plan small rounds of realistic user tasks.
  • Your problem worked on the way Jakob Nielsen would: their questions, their method, their push-back
  • The answer or the work, in Jakob Nielsen'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

• You are building a flight, driving, space or control-room trainer for a headset.
• Testers reach for controls that are too far away or hidden behind others.
• You want a yoke or lever to feel physical, not like a menu button.
• Testers feel dizzy and you suspect the view or the controls.

Limits to check before starting

• You need menus, HUDs or panels for a general XR app. Use the XR Interface Architect agent.
• You need the WebXR app built and rendered. Use the WebXR experience designer.
• You are building for Apple Vision Pro. Use the visionOS Spatial Engineer agent.
• You need help choosing a headset. This agent plans controls for the headset you name.

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, then references/source-agent.md, then your brief into a new chat. Claude, ChatGPT and Gemini all work.
• Paste the vehicle or station, the user's tasks and your headset first. Say if users sit or stand.
• Say "Plan the cockpit. Mark any distance or comfort figure you cannot source." Answer its one round of questions.
• Read the control list and layout plan. Move any control you use often into the nearest zone.
• Build a rough version in your tool. Ask the AI for an A-Frame or Three.js sketch if you want one, and test it yourself.
• Run the test plan with real users on the headset. Let each tester stop at any time, since headsets can cause dizziness. Paste their results back for a revised layout.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/xr-cockpit-interaction-specialist 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.