UX Evaluator FAQs

Question 1

Does this skill require Playwright to function?

Accepted Answer

While Playwright MCP is highly recommended for automated browser walkthroughs and evidence capture, the skill can also operate via manual user-provided walkthrough notes and screenshots if browser automation is unavailable.

Question 2

What information do I need to provide to start an evaluation?

Accepted Answer

You should provide the desired mode, a product context source (like a markdown file or Linear ID), a starting URL, the specific flow to test, and the required depth of the evaluation.

Question 3

What is the difference between ux-eval and dogfood modes?

Accepted Answer

The ux-eval mode focuses on quality assessment using the User Lifecycle Framework to check for heuristic adherence, while dogfood mode provides a phased approach that strictly separates the user perspective from technical debugging and infrastructure audits.

Question 4

Can I sync evaluation findings with my task manager?

Accepted Answer

Yes, the skill features optional Linear MCP integration. It can automatically create a new project and populate it with issues based on the findings, mapping severity levels to priority rankings.

Question 5

How does the technical debugger phase help developers?

Accepted Answer

In the Dogfooding workflow, the technical debugger takes findings from the user perspective and uses code-searching tools like 'rg' and 'read' to identify the specific files and logic causing the reported issues.

UX Evaluator

UX Evaluator

Key Features

Use Cases

Key Features

Use Cases