Borrowing it
Nothing to install: this file belongs to DDS-Solutions/AI-TadPole-OS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DDS-Solutions/AI-TadPole-OS/main/.agent/skills/web-design-guidelines/SKILL.mdgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/web-design-guidelines)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/web-design-guidelines/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/web-design-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01029 |
| Opus 5.5 | $0.00013 | $0.00412 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
web-design-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 12d 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.
This is a copy
80% identical to web-design-guidelines — 85 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / web-design-guidelines
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Missing keyboard focus indicators, non-semantic interactive divs, or WCAG contrast failures.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Web Interface Guidelines & Accessibility Protocol
Philosophy: Great web interfaces are accessible by default, navigable via keyboard, visually communicative, and responsive without jank.
Standard: Vercel Web Interface Guidelines & WCAG 2.2 AA.
Workflow Bindings: Integrated into/createand/ui-ux-pro-max.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/web_interface_guidelines_spec.md |
Vercel Web Interface Guidelines, focus ring styles, motion tokens, and contrast ratios | Designing interactive controls & verifying accessibility |
scripts/ui_guidelines_checker.py |
Automated static auditor for outline-none without focus-visible, clickable divs, and zoom restrictions |
Auditing frontend React/HTML components |
⚡ 1. Top 4 Non-Negotiable Interface Rules
- Focus Ring Affordance: Never strip focus rings with
outline: nonewithout providing an explicit:focus-visiblereplacement ring. - Semantic Buttons: Always use
<button type="button">for interactive clicks. Never attachonClickto a bare<div>or<span>without keyboard handlers androle="button". - Pinch-to-Zoom Freedom: Never disable mobile user scaling (
user-scalable=nois strictly forbidden). - Accessible Loading States: Buttons performing asynchronous tasks must display loading spinners and disable duplicate submissions.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago Changed · +10 lines · -11 tokens per session 3faca1e8f007
- 1mo ago First seen · 65 lines · 44 tokens per session scan A 33fdea14993d
web-design-guidelines is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,029 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to web-design-guidelines, differing in 85 lines, and is treated as a copy.
Other skills, from other repositories
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…
elements
Use this skill by default for any UI-related work or with NVIDIA Elements (nve-), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.
design-implementation-reviewer
Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity.
screenshot-to-code
Turns a screenshot, mockup, Figma export, or photo of a UI into working front-end code - React + Tailwind CSS v4 by default, or Next.js, Vue, or plain HTML/CSS - matching layout, spacing, colors, and typography, then renders the result and compares it against the image to close visual gaps. Use whenever the user…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.