uiux-reviewer

Review UI/UX documentation and append dated feedback to UIUX.md.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill uiux-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uiux-reviewer
Source: https://github.com/hoonzinope/skills/tree/main/uiux-reviewer
Command: npx skills add https://github.com/hoonzinope/skills --skill uiux-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

UI/UX documentation often lacks explicit reviews and risk notes, making it hard to track UX issues over time.

Core Features & Use Cases

  • Append: add a dated UI/UX Review section to the UIUX.md without editing the original content.
  • Guardrails: preserves source doc integrity and standardizes feedback using the provided checklist and template.
  • Reuse: enables teams to capture consistent UX observations for audits, handoffs, and reviews.

Quick Start

Append a new dated UI/UX review to .documents/uiux/UIUX.md using the scaffold tool.

Frequently Asked Questions about uiux-reviewer

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

FAQPage Schema
How do I review UI/UX documentation to identify UX risks and inconsistencies?

You can review UI/UX documentation by appending a dated review section to the UIUX.md file. This process identifies gaps, inconsistencies, and UX risks while preserving the original content using a standardized checklist and template.

Can I append feedback to UIUX.md without modifying the original document content?

Yes, the review process enforces guardrails that preserve source document integrity. It appends a new dated UI/UX review section with actionable notes without editing or altering the original documentation content.

What is the best way to standardize UX observations for product team handoffs?

Standardize UX observations by applying a checklist and template to generate consistent, traceable feedback. This enables product teams to capture uniform UX risk notes for audits, handoffs, and reviews across documentation.

Does UIUX documentation review require any specific dependencies or code changes?

No, the UIUX documentation review requires no dependencies and enforces no code changes. It operates purely on existing documentation by applying scaffold tools, checklists, and templates to append actionable feedback.

When should I use a checklist to audit UX standards in documentation?

Use a checklist to audit UX standards when you need to track UX issues over time, identify documentation gaps, or ensure cohesive standards across product teams. It provides traceable, actionable feedback for formal reviews.

How does appending a dated review section improve UI/UX documentation audits?

Appending a dated review section improves audits by creating a traceable history of UX observations and risk notes. It standardizes feedback format across teams without altering the original source document.