Hire an AI XR interface architect

Everything it can hand back

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

• An input plan with a main method and a backup for each task
• A flow from first look to done, with what the user sees at each step
• A placement plan for panels, menus and heads-up displays
• A list of comfort risks to watch
• Test experiments with tasks, measures and what counts as trouble

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 distances, angles, sizes or latency limits. Never state one as fact. Give a figure only as "starting point to test" and say to check the headset maker's guidance.
• Keep seated vehicle cockpits, WebXR builds and visionOS apps out of scope. Point to the XR Cockpit Interaction Specialist agent, the XR Immersive Developer agent or the visionOS Spatial Engineer agent.
• Do not invent a fact about the user's project. If a figure is not from the user, label it as an assumption.
• Test safety: tell the user that testers can feel dizzy or sick in a headset. They should be free to stop at any time, take breaks, and follow the headset maker's safety guidance.
• 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

• Stating a placement distance or comfort limit as a rule with no source.
• A single input method with no backup for a key task.
• Claiming the plan was tested on a headset.
• 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 designing a menu, dashboard or heads-up display for a headset app and need a layout plan.

• Input model. A main input and a backup for each task, and who each one helps.
• UI flow. Each step from first look to done, with what the user sees and does.
• Placement plan. Where each panel or menu sits, what it follows, and a starting distance and angle to test.
• Accessibility backups. For each task, the main input and the backup input.
• Comfort risks. Risks in the plan and how to check each one.
• Validation experiments. Tasks for testers, what to measure and what counts as trouble.

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

• Fix the brief. It confirms the app idea, tasks, device, environment and users. Gaps are asked once, then marked MISSING.
• Choose the inputs. It picks a main input for each task and a backup so more people can use the app.
• Map the flow. It writes the steps from first look to done, and what the user sees and does at each one.
• Place the interface. It places each panel or menu in space and says if it follows the world, the body or the head.
• Flag the risks. It lists comfort and discovery risks in the plan and says how to check each.
• Plan the tests. It writes experiments with tasks, measures 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-interface-architect 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-interface-architect/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

• Your app idea and the main tasks users do in it
• Your headset or device, and how users act: touch, gaze and pinch, controllers or gestures
• Where it is used: seated, standing or room-sized
• Users who need other input methods, such as limited hand use (optional)
• A sketch or the screens you have so far (optional)

Helpful context (optional)

• A sketch of your panels and menus
• Your headset maker's comfort and design guidance
• Notes on any users who cannot use hands or voice

Tools and access

• Claude, ChatGPT or Gemini: Any chat AI can write the flow and tables. Pick one that can read a sketch of your layout.

Functions and deliverables

• XR interface architect agent: Plan spatial UI for VR, AR and XR apps: panels, menus, input methods, comfortable placement and a test plan, from your app idea.
  • An input plan with a main method and a backup for each task
  • A flow from first look to done, with what the user sees at each step
  • A placement plan for panels, menus and heads-up displays
  • A list of comfort risks to watch
  • Test experiments with tasks, measures and what counts as trouble
  Source: Michael Sitarzewski and Agency Agents contributors.
• Mobile app designer: Share the platform, app flow and device needs. Get a touch-first design, feasibility review and device checks to run.
  • A risk score with a reason for each of the five points
  • A touch-first layout with the main action in thumb reach
  • Notes on what differs between iOS and Android
  • Loading, error and no-signal states
  • What to simplify first, if the score is low
  Source: sickn33.
• Expo app interface builder: Turn screen plans and an Expo project into Expo Router screens, controls, and code for motion.
  • Expo Router screen files in an app folder
  • Layout files that set up stacks and native tabs
  • A color theme file that works in light and dark mode
  • Motion, native controls, search and sheets where you asked for them
  • The list of packages to install
  Source: sickn33.
• Interface principles checker: Check your screen or flow against named UX principles. Get each problem, its severity and a fix, plus trust checks for AI screens.
  • Problems tied to named principles, ranked by severity, each with a fix
  • Common UX mistakes found, with where and how to fix them
  • Flow problems, such as hard choices, errors and missing feedback
  • Trust checks for AI screens, and a short UX brief for your coding AI if you ask
  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

• You are designing a menu, dashboard or heads-up display for a headset app and need a layout plan.
• Your app must work with hands, controllers and gaze, and you need to decide which one leads.
• Testers find the panels tiring, too close or hard to find.
• A developer needs a flow and layout template before they start coding.

Limits to check before starting

• Your app is a seated vehicle with levers and gauges. Use the XR cockpit interaction designer.
• You need the experience built in WebXR. Use the WebXR experience designer.
• You are building for Apple Vision Pro. Use the visionOS Spatial Engineer agent.
• Your screens are flat, on the web or a phone. Use the UI Designer agent.

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 your app idea, the main tasks and your headset first. Say where users will be: seated, standing or in a room.
• Say "Plan the interface. Mark any distance or angle as a starting point to test." Answer its one round of questions.
• Read the input plan first. Check that every key task has a backup input.
• Build rough panels in your tool, using the placement plan. Move them and see what feels tiring.
• Run the test experiments with real users on the headset. Let each tester stop at any time, since headsets can cause dizziness. Paste the results back for a revised plan.

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-interface-architect 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.