---
name: frontend-interface-review
description: "Improve a product interface\u2019s hierarchy, accessibility and interaction states. Use when the user requests frontend interface review. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Frontend Interface Review

Improve a product interface’s hierarchy, accessibility and interaction states.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- UI source or screenshots
- User task
- Existing design system
- Target devices

## Methods

### Walk the primary task

Walk the primary task and identify where users must guess, repeat information or recover from unclear states. Preserve established product terminology.

### Inspect interaction states

Inspect typography, spacing, contrast, focus, empty/error/loading states and responsive behavior. Prioritize observed usability defects before decoration.

### Implement coherent improvements

Propose or implement a coherent batch of improvements within the current design system. Respect reduced motion and avoid adding expensive effects to routine flows.

### Verify responsive usability

Verify the changed flow on desktop and mobile with keyboard use and realistic content lengths. Report what was inspected versus what remains a hypothesis.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.