web-interface-guidelines

A checklist for building and reviewing web interfaces, covering keyboard use, focus, touch targets, forms, layout, animation, content, performance, and accessibility.

In plain words
What is it for?
Use it when creating or reviewing websites and web apps, especially React or Next.js interfaces, to check interactions, responsive layouts, forms, loading states, and overall interface quality.
Why use it?
It helps catch common usability and accessibility problems before they reach users, such as invisible focus states, controls that are hard to tap, or forms that behave poorly on mobile.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/markerikson/opencode-config-example/web-interface-guidelines
Any agent
npx skills add markerikson/opencode-config-example --skill web-interface-guidelines
Clone the repo
git clone --depth 1 https://github.com/markerikson/opencode-config-example

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,689 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.02689
Opus 5 $0.00024 $0.01345
Sonnet 5 $0.00010 $0.00538
Haiku 4.5 $0.00005 $0.00269

Measured 2d ago against content hash 38249a8bee58, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

web-interface-guidelines scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

config/skill/web-interface-guidelines/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web Interface Guidelines

Source: Vercel Web Interface Guidelines — a living, non-exhaustive list of interface design decisions. Most guidelines are framework-agnostic, some specific to React/Next.js.

Interactions

  • Keyboard works everywhere. All flows are keyboard-operable & follow the WAI-ARIA Authoring Patterns.
  • Clear focus. Every focusable element shows a visible focus ring. Prefer :focus-visible over :focus to avoid distracting pointer users. Set :focus-within for grouped controls.
  • Manage focus. Use focus traps, move & return focus according to the WAI-ARIA Patterns.
  • Match visual & hit targets. Exception: if the visual target is < 24px, expand its hit target to >= 24px. On mobile, the minimum size is 44px.
  • Mobile input size. <input> font size is >= 16px on mobile to prevent iOS Safari auto-zoom/pan on focus.
  • Respect zoom. Never disable browser zoom.
  • Hydration-safe inputs. Inputs must not lose focus or value after hydration.
  • Don't block paste. Never disable paste in <input> or <textarea>.
  • Loading buttons. Show a loading indicator & keep the original label.
  • Minimum loading-state duration. If you show a spinner/skeleton, add a short show-delay (~150-300 ms) & a minimum visible time (~300-500 ms) to avoid flicker on fast responses. React <Suspense> does this automatically.
  • URL as state. Persist state in the URL so share, refresh, Back/Forward navigation work (e.g., nuqs).
  • Optimistic updates. Update the UI immediately when success is likely; reconcile on server response. On failure, show an error & roll back or provide Undo.
  • Ellipsis for further input & loading states. Menu options that open a follow-up (e.g., "Rename...") & loading/processing states (e.g., "Loading...", "Saving...", "Generating...") end with an ellipsis.
  • Confirm destructive actions. Require confirmation or provide Undo with a safe window.
  • Prevent double-tap zoom on controls. Set touch-action: manipulation.
  • Tap highlight follows design. Set webkit-tap-highlight-color.
  • Design forgiving interactions. Controls minimize finickiness with generous hit targets, clear affordances, & predictable interactions (e.g., prediction cones).
  • Tooltip timing. Delay the first tooltip in a group; subsequent peers have no delay.
  • Overscroll behavior. Set overscroll-behavior: contain intentionally (e.g., in modals/drawers).
  • Scroll positions persist. Back/Forward restores prior scroll.
  • Autofocus for speed. On desktop screens with a single primary input, autofocus. Rarely autofocus on mobile because the keyboard opening can cause layout shift.
  • No dead zones. If part of a control looks interactive, it should be interactive.
  • Deep-link everything. Filters, tabs, pagination, expanded panels — anytime useState is used.
  • Clean drag interactions. Disable text selection & apply inert while an element is dragged.
  • Links are links. Use <a> or <Link> for navigation so standard browser behaviors work (Cmd/Ctrl+Click, middle-click, right-click). Never substitute with <button> or <div>.
  • Announce async updates. Use polite aria-live for toasts & inline validation.
  • Locale-aware keyboard shortcuts. Internationalize keyboard shortcuts for non-QWERTY layouts. Show platform-specific symbols.

Read the full file on GitHub · 137 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 137 lines · 48 tokens per session scan A 38249a8bee58

Subscribe to this mod's changes

web-interface-guidelines is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 2,689 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

diagnostic-stem-delivery

Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.

HKUDS/OpenSpace · 23 tokens

vox-director

Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end on the Atlas Cloud API + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…

Alisa0808/vox-director · 236 tokens

seedance-vocab-ja

This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.

Emily2040/seedance-2.0 · 50 tokens

model-compatibility

Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.

artokun/comfyui-mcp · 47 tokens