detect-ux

Analyze a codebase to surface UX frictions and heuristic signals.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill detect-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-ux
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/detect-ux
Command: npx skills add https://github.com/parhumm/jaan-to --skill detect-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect-UX analyzes a codebase to surface UX frictions, journeys, and heuristic signals.

Core Features & Use Cases

  • Repo-driven UX audits that map user journeys, identify pain points, and highlight heuristic gaps.
  • Infers routes, flows, personas, JTBD, and accessibility signals from code signals and framework patterns.
  • Generates structured outputs for review and integration into product docs.

Quick Start

Run detect-ux on your repository to generate a UX detection report.

Frequently Asked Questions about detect-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UX friction and user journeys directly from a codebase?

Repo-driven UX audits analyze framework patterns and code signals to surface user journey frictions, inferring personas, JTBD, and accessibility signals with supporting code evidence.

What UX signals can be inferred from code repository analysis?

By examining framework patterns and code signals, repo analysis infers user flows, personas, JTBD, and accessibility signals to map user journeys and surface heuristic UX gaps.

Can I generate user personas and JTBD from framework patterns in my code?

Yes, applying heuristic analysis to your repository infers personas and JTBD from existing code signals and framework patterns, mapping user intent and flows directly from the codebase.

Does repo-driven UX auditing detect accessibility signals and pain points?

Yes, repo-driven UX auditing detects accessibility signals and user pain points by analyzing codebase framework patterns, producing structured outputs with evidence for product doc integration.

What is the best way to map user journeys using code signals from a repository?

Analyzing code signals and framework patterns to infer user flows provides the best way to map journeys from a repository, producing structured outputs that identify pain points and heuristic gaps.

Are there limitations to detecting UX heuristics without runtime user testing?

Detecting UX heuristics from a codebase relies solely on static code signals and framework patterns, meaning it surfaces structural friction and heuristic gaps but cannot capture runtime user behavior or real-time feedback.