Friction Auditor

Rigorous product audit of an already-built feature to detect UX friction, functional gaps, and user risk, then produce actionable, prioritized, and justified recommendations (never generic). Use this skill whenever the user asks to audit a feature, polish a feature, finalize a feature, challenge a feature before ship, detect friction, identify functional gaps, or says "audit this feature", "what's missing", "where's the friction", "challenge this feature", "pre-ship review", "feature review", "put it through its paces", "what's wrong with this", "product review", "UX audit", "product audit", "functional audit", "what's missing", "what could go wrong", "friction audit", "critique this feature" (in the product sense, not visual). Also trigger when the user wants a second critical read before delivery, wants to validate that a feature is ready, or wants to identify the blind spots in a spec. Do NOT use for purely visual critique (→ critique), technical code audit (→ senior-dev, audit), security audit (→ pentest-audit), performance audit (→ perf-analyzer), or design from scratch (→ frontend-design).

mkdir -p ~/.claude/skills/friction-auditor
curl -L https://claudskills.com/skills/friction-auditor/SKILL.md \
  -o ~/.claude/skills/friction-auditor/SKILL.md

@misc{friction-auditor-2026,
  author    = {tinkybeatz},
  title     = {Friction Auditor [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/friction-auditor/}
}