eightforge-ux-reviewer

Reviews operator-facing UI for workflow clarity, state honesty, and accessibility.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-ux-reviewer-ericanalysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eightforge-ux-reviewer
Source: https://github.com/EricAnalysis/eightforge-os/tree/main/.cursor/skills/eightforge-ux-reviewer
Command: npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-ux-reviewer-ericanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operational control interfaces often hide risk, flatten distinct system states into generic statuses, and force operators to hunt for blockers and next actions. This Skill provides a structured expert review of EightForge UI surfaces so that risk, evidence, and required actions are immediately visible and honestly represented. ## Core Features & Use Cases - State Honesty Review: Verifies that authority, compatibility, shadow, stale, partial, conflicted, blocked, and unresolved states remain visually and semantically distinct rather than collapsed into generic success or warning indicators. - Operator Workflow Audit: Checks information architecture, evidence navigation, action clarity, and relationship visualization against operator questions like what is wrong, what is at risk, and what happens next. - Accessibility and Hierarchy Checks: Evaluates keyboard access, focus order, contrast, semantic labels, and visual hierarchy emphasizing blockers and required human judgment. - Use Case: When reviewing a validator or execution page, run this Skill to receive a verdict (Pass, Pass with Concerns, or Fail) with severity-ordered issues, exact repository evidence, minimal fixes, regression risks, and suggested tests. ## Quick Start Review the project overview page for operator workflow clarity, state honesty, and accessibility using the EightForge UX review checklist.

Frequently Asked Questions about eightforge-ux-reviewer

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

FAQPage Schema
How do I review an operational dashboard UI for risk visibility?▼

Run a structured UX review that checks whether the interface answers what is wrong, what is at risk, what must be fixed first, and what happens next. The review produces a verdict with severity-ordered issues, exact evidence, and minimal fixes.

What should a UX review checklist for control systems include?▼

It should cover information architecture matching operator mental models, state honesty across stale and blocked states, evidence navigation, action clarity, accessibility, and visual hierarchy emphasizing blockers. Each finding should cite repository evidence and the smallest correction.

How do I keep loading, empty, and error states honest in a web app?▼

Map each UI state directly to backend reality and avoid ambiguous done indicators when work remains. Distinguish stale, partial, conflicted, blocked, and unresolved states in both language and presentation rather than flattening them into generic warnings.

When should UX review findings be routed to other specialist reviewers?▼

Route upstream truth and authority questions to a truth-engine reviewer, execution mechanics to an execution reviewer, audit-history semantics to an audit reviewer, and heavy rendering concerns to a performance reviewer. The UX reviewer owns operator interaction and presentation only.

Why does my UI show misleading status even when backend data is correct?▼

This happens when components recompute truth, precedence, or validation locally instead of consuming resolved upstream state, or when distinct states are collapsed into generic chips. The fix is to format and filter resolved projections without rederiving them.