ehmoehmo/platform-design-skills/skills/web/AGENTS.md

platform-design-skills / web

AGENTS.md603 starsChanged 8 months agoMITView on GitHub

Framework-agnostic web design and accessibility guidelines based on WCAG 2.2, MDN Web Docs, and modern web platform standards.

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/android/AGENTS.mdAGENTS.md
- skills/ios/AGENTS.mdAGENTS.md
- skills/ipados/AGENTS.mdAGENTS.md
- skills/macos/AGENTS.mdAGENTS.md
- skills/tvos/AGENTS.mdAGENTS.md
- skills/visionos/AGENTS.mdAGENTS.md
- skills/watchos/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- android-design-guidelinesSkill
- ios-design-guidelinesSkill
- ipados-design-guidelinesSkill
- macos-design-guidelinesSkill
- tvos-design-guidelinesSkill
- visionos-design-guidelinesSkill
- watchos-design-guidelinesSkill
- web-design-guidelinesSkill

The file

We split this AGENTS.md into the rules it gives an agent

10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Never use <div onclick> when <button> exists — use semantic HTML
line 50
Very specific:
Never set maximum-scale=1 or user-scalable=no in the viewport meta tag
line 51
Distinctive:
Never rely on color alone to convey information — pair with text or icons
line 52
Distinctive:
Never use placeholder text as the only label for a form input
line 53
Very specific:
Never build interactive elements that are only keyboard-accessible via tabindex > 0
line 54
Very specific:
Never omit alt attributes on images — use alt="" for decorative images
line 55
Distinctive:
Never animate content that flashes more than 3 times per second (seizure risk)
line 56
Distinctive:
Never trap keyboard focus inside a component without providing a documented escape
line 57
Very specific:
Never use <table> for layout — tables are for tabular data only
line 58
Very specific:
Never set font-size in px on body text — use rem so user preferences apply
line 59

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

Web Platform Design Skills

Purpose

Framework-agnostic web design and accessibility guidelines based on WCAG 2.2, MDN Web Docs, and modern web platform standards.

File Structure

web/
  metadata.json        # Version, references, abstract
  SKILL.md             # Full guidelines (load this)
  AGENTS.md            # This file
  rules/
    _sections.md       # Sectioned rules for selective loading

Usage

Load SKILL.md for complete guidelines when building or reviewing web UI.
Load rules/_sections.md for individual category rules when working on a specific concern (e.g., only accessibility, only forms).

When to Apply

Building HTML/CSS/JS interfaces
Auditing accessibility or WCAG compliance
Implementing responsive layouts
Reviewing web UI pull requests
Optimizing web performance
Adding dark mode or theming
Internationalizing web content

Priority Levels

Level	Categories
CRITICAL	Accessibility/WCAG, Responsive Design
HIGH	Forms, Typography, Performance
MEDIUM	Animation, Dark Mode, Navigation, Touch, i18n, Progressive Web Apps

Conventions

Rules use imperative voice ("Use semantic HTML", not "You should use").
Code examples are vanilla HTML/CSS/JS unless noted.
WCAG success criteria referenced as (SC x.x.x).
Priority in brackets: [CRITICAL], [HIGH], [MEDIUM].

Never Do

Never use <div onclick> when <button> exists — use semantic HTML
Never set maximum-scale=1 or user-scalable=no in the viewport meta tag
Never rely on color alone to convey information — pair with text or icons
Never use placeholder text as the only label for a form input
Never build interactive elements that are only keyboard-accessible via tabindex > 0
Never omit alt attributes on images — use alt="" for decorative images
Never animate content that flashes more than 3 times per second (seizure risk)
Never trap keyboard focus inside a component without providing a documented escape
Never use <table> for layout — tables are for tabular data only
Never set font-size in px on body text — use rem so user preferences apply

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free