Web Interface Guidelines

Community

xuansenpa1

web-interface-guidelines

Vercel's comprehensive UI guidelines for building accessible, performant web interfaces. Use this skill when reviewing or building UI components for compliance with best practices around accessibility, performance, animations, and visual stability.

Overview

Publisher	xuansenpa1
Repository	`skillrevise`
Skill name	`web-interface-guidelines`
Stars	56
Forks	3
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by xuansenpa1 on GitHub. Read the source before you install it.

Installation

Install the Web Interface Guidelines AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/xuansenpa1/skillrevise/tree/main/data/skillsbench/tasks/fix-visual-stability/environment/skills/web-interface-guidelines
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/xuansenpa1/skillrevise/tree/main/data/skillsbench/tasks/fix-visual-stability/environment/skills/web-interface-guidelines

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/xuansenpa1/skillrevise.git /tmp/skillrevise
mkdir -p .claude/skills
cp -r /tmp/skillrevise/data/skillsbench/tasks/fix-visual-stability/environment/skills/web-interface-guidelines .claude/skills/web-interface-guidelines

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Web Interface Guidelines in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Web Interface Guidelines on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Web Interface Guidelines is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Web Interface Guidelines

Review UI code for compliance with Vercel's web interface standards.

Quick Reference - Visual Stability

Issue	Rule
Images without dimensions	`<img>` needs explicit `width` and `height` (prevents CLS)
Font loading flash	Critical fonts: `<link rel="preload" as="font">` with `font-display: swap`
Large lists	Virtualize lists >50 items (`content-visibility: auto`)
Layout reads in render	No `getBoundingClientRect`, `offsetHeight` in render path

Full Rules

Images

<img> needs explicit width and height (prevents CLS)
Below-fold images: loading="lazy"
Above-fold critical images: priority or fetchpriority="high"

Performance

Large lists (>50 items): virtualize (virtua, content-visibility: auto)
No layout reads in render (getBoundingClientRect, offsetHeight, offsetWidth, scrollTop)
Batch DOM reads/writes; avoid interleaving
Add <link rel="preconnect"> for CDN/asset domains
Critical fonts: <link rel="preload" as="font"> with font-display: swap

Accessibility

Icon-only buttons need aria-label
Form controls need <label> or aria-label
Interactive elements need keyboard handlers (onKeyDown/onKeyUp)
<button> for actions, <a>/<Link> for navigation (not <div onClick>)
Images need alt (or alt="" if decorative)

Focus States

Interactive elements need visible focus: focus-visible:ring-* or equivalent
Never outline-none / outline: none without focus replacement
Use :focus-visible over :focus (avoid focus ring on click)

Animation

Honor prefers-reduced-motion (provide reduced variant or disable)
Animate transform/opacity only (compositor-friendly)
Never transition: all—list properties explicitly

Forms

Inputs need autocomplete and meaningful name
Use correct type (email, tel, url, number) and inputmode
Never block paste (onPaste + preventDefault)
Labels clickable (htmlFor or wrapping control)

Content Handling

Text containers handle long content: truncate, line-clamp-*, or break-words
Flex children need min-w-0 to allow text truncation
Handle empty states—don't render broken UI for empty strings/arrays

Anti-patterns (flag these)

user-scalable=no or maximum-scale=1 disabling zoom
transition: all
outline-none without focus-visible replacement
Images without dimensions
Large arrays .map() without virtualization
Form inputs without labels
Icon buttons without aria-label

Frequently asked questions

What does the Web Interface Guidelines AI skill do?

Why use Web Interface Guidelines on TypingMind?

Because you install it once and use it with any model. Web Interface Guidelines is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Web Interface Guidelines in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/xuansenpa1/skillrevise/tree/main/data/skillsbench/tasks/fix-visual-stability/environment/skills/web-interface-guidelines. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Web Interface Guidelines?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Web Interface Guidelines?

As many as you like. As long as a model supports skills, you can use Web Interface Guidelines with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Web Interface Guidelines AI skill free?

Yes. It is published on GitHub by xuansenpa1 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Tensorrt Llm

NousResearch

OrganizationPopular

High-throughput LLM inference on NVIDIA GPUs.

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal…

Claude Opus 4 5 Migration

anthropics

OrganizationPopular

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string…

Deploy Release Test

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Web Interface Guidelines

Quick Reference - Visual Stability

Full Rules

Images

Performance

Accessibility

Focus States

Animation

Forms

Content Handling

Anti-patterns (flag these)

Frequently asked questions

Related AI Skills

Set up your own AI workspace now