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.
npx skills add smicolon/ai-kit --skill web-design-guidelinesgit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/smicolon/ai-kit/web-design-guidelines)<a href="https://agentmods.dev/skills/smicolon/ai-kit/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/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/smicolon/ai-kit/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/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.00030 | $0.00460 |
| Opus 5.5 | $0.00012 | $0.00184 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
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 1mo 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.
What it actually says
Web Interface Guidelines
Auditing rules for React, Next.js, and web frontend UI reviews.
Core Review Checkpoints
1. Typography & Hierarchy
- Headings use semantic tags (
<h1>to<h6>) in logical order without skipping levels. - Line heights and letter spacing maintain readable proportions (
leading-relaxedorleading-normalfor body text). - Avoid fixed pixel font sizes; use responsive Tailwind classes (
text-sm,text-base,text-lg).
2. Interactive States & Affordances
- Hover, Focus, and Active states: Every interactive element (
<button>,<a>,<input>) must have discernible hover, focus-visible, and active states. - Focus Rings: Never use
outline-nonewithout providing an accessiblefocus-visible:ring-2 focus-visible:ring-offset-2replacement. - Loading & Disabled States: Interactive buttons triggering async actions must indicate loading and be disabled to prevent duplicate submissions.
3. Touch Targets & Mobile Usability
- Minimum touch target size for mobile/tablet is 44x44px (or
min-h-[44px] min-w-[44px]). - Adequate padding between adjacent interactive elements to prevent mis-taps.
4. Color & Contrast
- Text meets WCAG 2.1 AA minimum contrast ratio:
- Normal text: 4.5:1
- Large text (18pt / 24px+ or 14pt bold): 3:1
- Colors are not the sole indicator of state (always pair color changes with icons, underline, or text labels).
5. Layout & Responsive Behavior
- No horizontal scrollbars on viewport widths from 320px up to 4K.
- Use CSS grid or flexbox with wrapping (
flex-wrap). - Modals and popovers lock body scroll when open and dismiss on
Escapekey or backdrop click.
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.
- 1mo ago First seen · 37 lines · 30 tokens per session scan A 5653a4388b29
web-design-guidelines is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 460 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
ui-html-renderer
Use this specialist for unusually complex stateful HTML, blank/runtime-risk repair, strict source-to-HTML fidelity, reusable component galleries, brand boards, or detailed implementation handoff. Ordinary single-page HTML uses ui-design-executor, which already preserves HTML-default delivery and baseline…
product-ui
Use this skill when UI design and UI implementation should happen together. It turns product context into usable frontend screens, components, layout decisions, design-system choices, accessibility rules, and visual polish.
impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
brand-tokens
A reference library of visual design rules for well-known brands, including colors, fonts, corner shapes, and explanations of each brand's visual style. Design tokens are reusable values that keep an interface's appearance consistent.
component-design
Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.
ui-aesthetic
A set of visual design rules for making web pages and components look consistent and readable. It covers icons, colors, typography, spacing, text, accessibility contrast, layout, and restrained animation.