Borrowing it
Nothing to install: this file belongs to richardthe3rd/cambridge-beer-festival-app. 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/richardthe3rd/cambridge-beer-festival-app/main/.claude/skills/ui-and-accessibility/SKILL.mdgit clone --depth 1 https://github.com/richardthe3rd/cambridge-beer-festival-appWrote 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/richardthe3rd/cambridge-beer-festival-app/ui-and-accessibility)<a href="https://agentmods.dev/skills/richardthe3rd/cambridge-beer-festival-app/ui-and-accessibility"><img src="https://agentmods.dev/badge/skills/richardthe3rd/cambridge-beer-festival-app/ui-and-accessibility/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/richardthe3rd/cambridge-beer-festival-app/ui-and-accessibility"><img src="https://agentmods.dev/badge/skills/richardthe3rd/cambridge-beer-festival-app/ui-and-accessibility.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.00189 | $0.06527 |
| Opus 5 | $0.00095 | $0.03263 |
| Sonnet 5 | $0.00038 | $0.01305 |
| Haiku 4.5 | $0.00019 | $0.00653 |
Grade A, and why
ui-and-accessibility 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.
How it starts
The opening of the file, as written. The whole thing — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI and Accessibility
This skill has two jobs, in priority order:
- Stop UI changes from becoming redesigns. This is not a style preference — it is the single costliest failure mode in this project's history (maintainer-confirmed).
- Give you the accessibility and widget-pattern catalogue so new UI meets the bar this project already holds, without re-deriving it from scratch.
If you are only changing lib/domain/, lib/providers/, or lib/services/ with
no visible UI change, see skill architecture-contract instead — this skill
does not apply. If you're only fixing/writing tests, see validation-and-qa. If
you're implementing the My Festival campaign end-to-end, see my-festival-campaign
for sequencing — come back here for the visual/accessibility rules it must follow.
Part 1 — UI-change discipline (read this first, every time)
Why this section exists
The project's principal engineer built this app largely solo, now with AI agents doing most of the typing. A sweeping visual redesign — restyle and restructure several screens in one pass — produces a diff too large for one human to review carefully, and too large for an agent to verify against the accessibility bar without missing something. Past redesigns cost more engineering time than any other category of change in this repo's history. The rules below exist because that failure mode is expensive and it has already happened.
The hard rules
-
One widget or one screen per PR. Do not restyle
DrinksScreenandDrinkCardandFestivalHeaderin the same change. If a task seems to need all three, split it into sequential PRs — each independently reviewable and revertible. -
Restyle OR restructure — never both in the same change.
- Restyle = colours, spacing, typography, icons, chip shapes — the widget tree shape is unchanged.
- Restructure = changing which widgets exist, how they nest, or what data flows into them.
- Mixing the two means a visual regression and a logic regression look
identical in the diff — you cannot
git revertone without the other, and a reviewer cannot separate "this looks different" from "this broke."
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 First seen · 517 lines · 189 tokens per session scan A 79c6d4290aef
ui-and-accessibility is a skill published in the GitHub repository richardthe3rd/cambridge-beer-festival-app (2 stars, last pushed yesterday), licensed MIT. It adds 189 tokens to every session and 6,527 once invoked, about $0.0009 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-31.
Other skills, from other repositories
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.