Skip to content

user-experience:evaluate misses below-the-fold actions, ambiguous view copy and stale in-product screenshots #7655

Description

@kyle-sexton

Problem

An expert review with /user-experience:evaluate on a live, multi-view web app missed three classes of problem that a person found by hand in minutes:

  1. Primary action below the fold. A question's answer buttons sat about 1,700 px down on desktop because an inline screenshot was enlarged. The skill names no screen sizes and never asks whether the main action is visible without scrolling.
  2. Ambiguous copy across views. A question asked "what would you change about this page?" in an app with three views. The heuristics review the interface, but no step reads the questions, labels and instructions the app shows people.
  3. Stale in-product pictures. Screenshots of the product shown inside the product came from older builds (a retired toolbar, a fake notification badge) and were upscaled. No step compares in-product pictures with the live screen or checks natural against displayed size.

Proposed changes (one line each, to the evaluate method)

  • For a live app, walk each task at a phone, a tablet and a desktop size, and record per step whether the primary action and the thing being asked about are on screen without scrolling.
  • Read every question, label and instruction the app shows people, and flag words such as "this page", "here" or "this one" that could point at more than one view, element or device.
  • Compare every screenshot or picture of the product shown inside it with the live screen and theme the viewer is on, and check each image's natural size against its displayed size; a mismatch or an upscale is a finding.

Acceptance

  • Each change lands with an eval case that fails before it (a page with a below-the-fold primary action; an ambiguous "this page" question; an upscaled, out-of-date in-product screenshot) and passes after.
  • Existing evaluate evals show no loss.

No related issue: found while dogfooding a multi-person interview page prototype.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Thanks for the detailed writeup. I understood this as three gaps in /user-experience:evaluate: it doesn't check multi-device fold visibility of the primary action, doesn't scan on-screen copy for view-ambiguous references ("this page"), and doesn't compare in-product screenshots against the live screen/theme or check for upscaling. The proposed changes and acceptance criteria (new failing-then-passing eval cases per gap, no regression in existing evals) are concrete enough to act on without further clarification. I didn't find an existing open issue covering the same gaps. No related-issue link was given, which matches the "found while dogfooding" note in the body.

    Automated triage. A maintainer reviews it.

  3. added
    help wantedMaintainer would welcome help.
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 16, 2026
  4. kyle-sexton commented on Oct 18, 2026

    @kyle-sexton
    MemberAuthor

    Agent Brief

    Type: Feature
    Summary: Add fold visibility, view-ambiguous copy and stale in-product picture checks to the /user-experience:evaluate expert review of a live app.

    Current behavior:
    An expert review of a live, multi-view web app does not check whether the primary action is visible without scrolling at any screen size, does not read the questions, labels and instructions the app shows, and does not compare pictures of the product shown inside it with the live screen.

    Desired behavior:
    For a live app the method:

    • walks each task at a phone, a tablet and a desktop size and records per step whether the primary action and the thing being asked about are on screen without scrolling;
    • reads every question, label and instruction the app shows and flags words such as 'this page', 'here' or 'this one' that could point at more than one view, element or device;
    • compares each screenshot or picture of the product shown inside it with the live screen and theme, and checks natural against displayed size; a mismatch or an upscale is a finding.

    Key interfaces:

    • The evaluate skill's expert-review method for a live app.
    • Its eval set (skill-creator evals.json format).

    Acceptance criteria:

    • The method states all three checks (read from the diff).
    • evals.json gains three cases: a page whose primary action sits below the fold at desktop size, whose expectations require the fold finding; a 'what would you change about this page?' question in a three-view app, whose expectations require the ambiguity finding; an upscaled, out-of-date in-product screenshot, whose expectations require the mismatch finding.
    • The existing eval cases are unchanged (read from the diff).
    • The user-experience plugin version is bumped with a CHANGELOG entry.

    Out of scope:

    • Running the evals to show each new case fails before and passes after, and the no-loss check on existing evals (paid eval run, after merge).
    • Other user-experience skills.

    This was generated by AI during backlog shaping. Held, not admitted: this brief is drafted and checked, but the issue lane would stop on it today. It is admitted, by adding agent-ready, once the lane can run the skill-quality check scripts (Automation Lanes' PR #7912). Held under the owner's 2026-10-18 lane-narrowing course correction.

  5. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    and removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.help wantedMaintainer would welcome help.priority: mediumReal value, no hard deadline; normal backlog flow.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Fields

    No fields configured for Feature.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions