← All runbooks
vercel-labs / web-design-guidelines

Web Interface Guidelines

Review UI code files for compliance with the Vercel Web Interface Guidelines. The agent reads the specified files and checks them against a comprehensive set of rules covering accessibility, focus states, forms, animation, typography, content handling, images, performance, naviga

agent claude-codemodel claude-sonnet-4-6snapshot python312-uveval programmatic5 stepsv1.0.0

Deploy Web Interface Guidelines to your jetty.io

One-click installs this runbook into a collection on your Jetty account. You can run it from the Spot dashboard, schedule it, or pipe inputs in via the API.

Deploy on jetty.io →View source
The shape of the run

5 steps · start to finish.

  1. 1
    Step 1

    Environment Setup

    ▶

    Verify the target files exist and are readable before proceeding.

    echo "=== Environment Setup ==="
# Confirm arguments were supplied
if [ -z "$ARGUMENTS" ]; then
  echo "ERROR: No file or pattern specified. Pass the target via ARGUMENTS."
  exit 1
fi

# Expand the pattern and confirm at least one file matches
FILES=$(ls $ARGUMENTS 2>/dev/null)
if [ -z "$FILES" ]; then
  echo "ERROR: No files found matching pattern: $ARGUMENTS"
  exit 1
fi

echo "Files to review:"
echo "$FILES"
echo ""
mkdir -p /app/results
  2. 2
    Step 2

    Read and Analyse Files

    ▶

    For each file matching `$ARGUMENTS`, read its content and check it against every rule category below. Record each violation as a finding.

  3. 3
    Step 3

    Write Review Report

    ▶

    Write `/app/results/review_report.md` using the output format below. Group findings by file. Use `file:line` references (VS Code clickable). Be terse—state issue and location. Skip explanation unless fix is non-obvious. No preamble.

  4. 4
    Step 4

    Iterate on Errors (max 3 rounds)

    ▶

    If any rule categories were skipped or files were unreadable:

  5. 5
    Step 5

    Write Summary

    ▶

    Write `/app/results/summary.md` with: