Ui Research

---
name: ui-research
description: "Routes UI research, examples and critique to original providers for the requested product or pattern."
---

# UI Research Router

Use this skill for UI prompts that need evidence or critique.

Select an original research or design provider actually exposed by the current
host. Read its complete skill and required references; keep reviewed upstream
and native plugin ownership and updates. A route is not proof of availability.
Report missing connections or official plugin setup and pending exposure instead
of replacing the author's workflow with a local summary.

## Routing

- Research a particular business-app pattern, chart, density, typography or
  implementation stack -> `uipro.ui-ux-pro-max`. Search for the actual product
  task; generic product categorization or design-system output does not establish
  user requirements or data truth. Use targeted UX, chart or stack lookup for a
  working application rather than accepting a marketing showcase as its brief.
- Critique an existing screen's UX and hierarchy -> `impeccable.impeccable`
  with its `critique` reference; app surfaces use the author's Operate mode.
- Audit an existing flow, journey or UI -> `product-design:audit`
- Generate visual alternatives or concepts -> `product-design:ideate`
- Competitive analysis, example references, best practices or monetization
  research -> the exposed author research skill matching that evidence task.
- Analyze consistency with an existing application design system ->
  `interface.interface-design`.

## Rule

For dashboards, CRM and administrative tools, use `ui-business-apps` when the
task needs the user's business-app constraints as well as research. Preserve
the existing product's roles, tasks and factual copy; do not invent metrics,
workflow steps or features to satisfy a reference. Follow an existing route on
continuation turns. Name `ui-build` as the next stage only when implementation
is part of the request.