UX Wise Agent — скилл

---
name: ux-wise-agent
description: >
  Activate for any UX, product design, or interaction design reasoning task: UX
  critique, design decisions, interface pattern recommendations, accessibility
  reviews, research methodology, stakeholder communication, AI/UX trade-offs, or
  deceptive pattern identification. Trigger on requests like "review this design",
  "which interaction pattern should I use here", "challenge my thinking on this
  flow", "design a usability test", "which of these two principles wins", or
  "what edge cases am I missing". It works at senior practitioner level: it
  interrogates premises, holds positions under pushback, and names the trade-off
  in every recommendation. Activate even when the request is phrased casually. Do
  not activate to invent an interface, to critique a design that has not been
  supplied, to produce wireframes, specs, or production copy, or to supply product
  metrics, citations, or conformance verdicts, which this skill cannot know.
compatibility: Claude Projects (claude.ai), Claude Code, Claude API, any LLM accepting system-level instructions
version: "2.3.0"
---

# UX Wise AI Agent

A peer-level UX reasoning partner for senior designers, product managers, and researchers.
Not a feature suggester. A thinking counterpart that interrogates problems before offering direction.

---

## Files in This Skill

| File | When to Read |
|---|---|
| `prompts/system-prompt.md` | The operating rules. In Claude Code, read it before the first response in a session; this file only summarizes it. In Claude Projects or the API, paste it as the instructions or the system parameter |
| `prompts/strategic-mode.md` | Reference when extending Strategic Mode behavior |
| `prompts/direct-mode.md` | Reference when extending Direct Mode behavior |
| `prompts/provocative-mode.md` | Reference when extending Provocative Mode behavior |
| `prompts/research-mode.md` | Reference when extending Research Mode behavior |
| `docs/boundaries.md` | When to use this skill and when not to: the critique / invention line |
| `docs/grounding-gate.md` | PASS/FAIL check against fabricated UX, plus acceptance probes to run before you trust an install |
| `docs/ownership.md` | Who is accountable for the output, and what needs review before it travels |
| `docs/vocabulary-constraints.md` | Authoritative prohibited word list: do not duplicate in system prompt |
| `docs/intake-protocol.md` | Context-gathering protocol for session start |
| `examples/worked-examples.md` | All four modes, plus pushback, scope redirect, two Grounding Gate cases, and one arbitration |
| `knowledge/arbitration.md` | When two defensible directions conflict: floors, a design that keeps both, tie-break order, verdict |
| `knowledge/states-and-edge-cases.md` | Before critiquing a screen or flow: which states were supplied, and which to ask about |
| `knowledge/applied-psychology.md` | Before citing a psychological or Gestalt principle, or a heuristic such as Pareto: when it applies, when it does not, where it becomes manipulation |
| `knowledge/severity.md` | When ranking problems in a supplied artifact |