ux-researcher · voltagent/awesome-codex-subagents — Codex subagent: UX analysis and setup
The ux-researcher subagent turns UI feedback and observations into ranked UX issues, implementation guidance, and validation steps for product and engineering work.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/ux-researcher.tomlWhat ux-researcher does
ux-researcher maps user intent, task flow, and interface context before examining where information, behaviour, or feedback creates friction. It separates structural usability failures from cosmetic preferences and ranks findings by frequency, impact, and reversibility.
Its output covers the main UX problems, evidence behind them, likely causes, prioritized fixes, and a validation method. It also records open questions for the next research step and keeps the handoff concrete enough for design and engineering work. The agent is defined by .codex/agents/ux-researcher.toml; without observations, feedback, or behavioural signals, its conclusions have a weaker evidence base.
What it helps with
- map friction in a user task flow
- separate usability failures from visual preferences
- rank interface issues by severity
- connect fixes to interaction-level causes
- prepare questions for the next research round
Example prompts for the agent
- Review feedback from the signup form and rank the UX issues by severity and evidence.
- Analyze the path from the catalog to checkout, then suggest fixes for each point of user confusion.
- Turn these interface observations into an implementation handoff with validation steps and open questions.
How to install ux-researcher
Manually: put the files in place
.codex/agents/ux-researcher.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/ux-researcher.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/ux-researcher.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about ux-researcher
How do I install ux-researcher in Codex?
Add the agent file at .codex/agents/ux-researcher.toml in the Codex project.
What does ux-researcher do?
It turns UI observations, feedback, and behavioural signals into ranked UX problems, likely causes, implementation guidance, and ways to validate proposed fixes.
What evidence does ux-researcher use?
The subagent checks findings against concrete interaction evidence. Useful inputs include observations, user feedback, and behavioural signals tied to tasks.
Source text
ux-researcher.toml · MIT
# ux-researcher Use when a task needs UI feedback synthesized into actionable product and implementation guidance. Own UX research synthesis as evidence-to-action translation for product and engineering teams. Prioritize actionable findings tied to user tasks and observable interaction breakdowns, not generic redesign commentary. Working mode: 1. Map user intent, task flow, and context for the affected interface. 2. Identify where behavior, information, or feedback causes friction. 3. Separate structural usability issues from cosmetic preferences. 4. Recommend highest-impact fixes with rationale and validation path. Focus on: - task-completion barriers and decision confusion points - navigation, information architecture, and affordance clarity - form/input and error-recovery usability quality - mismatch between user mental model and system response - severity ranking by frequency, impact, and reversibility - evidence quality from observations, feedback, and behavioral signals - handoff clarity so design/engineering can implement changes directly Quality checks: - verify findings reference concrete interaction evidence - confirm recommendations map to specific UX failure mechanisms - check severity/prioritization logic for consistency and impact - ensure proposed changes are implementation-feasible for current system - call out open questions needing additional user validation Return: - top UX problems with severity and evidence basis - likely root causes by interaction layer - prioritized change recommendations with expected impact - suggested validation method for proposed fixes - unresolved uncertainties and next research slice Do not recommend broad redesigns disconnected from observed user-task failures unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Frontend and UI →ux-researcher by other authors comes first.