Skip to content

2001105254-netizen/RacePulsePH / .agents/skills/iso-ui-layout-auditor

iso-ui-layout-auditor

Verified

Critique, audit, and refactor web and mobile UI screenshots or React/Tailwind code into high-density, zero-waste layouts governed by ISO ergonomics standards with separate Desktop (100vh) and Mobile (100dvh) checklists and blueprints. Use when auditing or refactoring consoles, dashboards, or field-staff views.

references/iso-9241-110.md

View on GitHub
# ISO 9241-110: Interaction Principles

## Standard Identity & Scope

- **Designation:** ISO 9241-110 (Ergonomics of human-system interaction, Part 110: Interaction principles; 2020 edition updated terminology from "dialogue principles" to "interaction principles").
- **Scope:** Technology-independent interaction principles for designing and evaluating interactive systems so user workflows stay predictable, transparent, controllable, and resilient to operator error.

## Core Principles Audited by This Skill

1. **Suitability for the task:** Expose only the controls, fields, and metrics needed for the active operational workflow; strip decorative banners, marketing copy, and irrelevant steps.
2. **Self-descriptiveness:** Make system state, active filters, selected context, and next valid actions immediately legible from the current viewport without memorizing hidden modes.
3. **Conformity with user expectations:** Honor established operational conventions (`Ctrl+F` focuses search, `Escape` closes modals/sheets, destructive actions sit apart from primary commit actions).
4. **Learnability:** Maintain consistent terminology, shortcut hints, and stable control positions across modules so new staff can operate consoles rapidly.
5. **Controllability:** Keep the operator in command of pace and sequence; preserve unsaved inputs on cancellation or network delay, and allow undo or mode switching without losing work.
6. **Use error robustness (error tolerance):** Guard irreversible or destructive actions (`Reset`, `Delete`, `Clear Reads`, `Disqualify`) behind explicit safety locks, typed or two-step confirmation, and non-destructive recovery paths.
7. **User engagement:** Keep feedback immediate and unambiguous so operators stay confident during high-tempo live operations.

## Desktop Console Criteria (`1080p` / `1366x768`, `100vh`)

- **Zero-navigation-tax workflow:** Keep the primary queue/table and its action dock visible together (`64%` / `36%`) so operators never lose visual context while entering data or scanning.
- **Explicit keyboard accelerators:** Surface `F1`-`F4`, `Ctrl+F`, and `Space` keycaps on high-frequency triggers, and suppress global hotkeys whenever focus is inside `<input>`, `<textarea>`, or `<select>`.
- **Destructive safety locks:** Separate `Reset` / `Delete` controls from primary `Commit` / `Save` buttons by spatial gap or a visual divider, and require confirmation via an in-app dialog (`DialogSurface`) or explicit arming toggle.
- **Preserved draft state:** Validation failures or API timeouts must leave operator inputs populated and display inline, field-adjacent error guidance.

## Mobile Field-Staff Criteria (`390x844`, `100dvh`)

- **Clear primary verb in the thumb dock:** Place one unmistakable primary CTA (`Scan Race Bib QR`, `Check In`, `Assign Chip`) in the sticky bottom bar; demote secondary or destructive options to an overflow sheet.
- **Accidental-tap prevention:** Never place `Delete` or `Reset` next to `Confirm` in the bottom thumb zone; require a deliberate modal confirmation before mutating live records.
- **State continuity on sheet close:** Closing or swiping down a control bottom sheet must not discard unsaved search filters or scroll position in the runner list.

## React & Tailwind Audit Patterns

```tsx
// Guarded destructive button: isolated from primary CTA and gated by confirmation dialog
<div className="flex items-center justify-between gap-3 pt-3 border-t border-[var(--border-default)]">
  <button
    type="button"
    onClick={onRequestReset}
    className="min-h-11 px-3 rounded-lg border border-red-600/40 text-red-600 hover:bg-red-500/10 text-sm font-semibold"
  >
    Reset Queue
  </button>
  <button
    type="button"
    onClick={onCommitPrimary}
    className="min-h-11 px-4 rounded-lg bg-red-600 text-white hover:bg-red-700 text-sm font-semibold"
  >
    Confirm Check-In (F1)
  </button>
</div>
```

## Inspection Evidence

- Verify every destructive action (`Reset`, `Delete`, `Clear`) triggers a confirmation gate rather than mutating state on single click (`C-2`, `R-26`).
- Verify `F1`-`F4`, `Ctrl+F`, `Space`, and `Escape` work via keyboard without triggering while typing inside form controls (`R-32`).
- Verify error, empty, and loading states preserve draft inputs and explain recovery clearly (`R-27`).
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall