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 jimtin/production-ai --skill frontend-design-qualitygit clone --depth 1 https://github.com/jimtin/production-aiWrote 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/jimtin/production-ai/frontend-design-quality)<a href="https://agentmods.dev/skills/jimtin/production-ai/frontend-design-quality"><img src="https://agentmods.dev/badge/skills/jimtin/production-ai/frontend-design-quality/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/jimtin/production-ai/frontend-design-quality"><img src="https://agentmods.dev/badge/skills/jimtin/production-ai/frontend-design-quality.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.00088 | $0.01012 |
| Opus 5 | $0.00044 | $0.00506 |
| Sonnet 5 | $0.00018 | $0.00202 |
| Haiku 4.5 | $0.00009 | $0.00101 |
Grade A, and why
frontend-design-quality 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Quality
Core Standard
Treat frontend work as complete only when the implemented flow is usable, visually coherent, and verified across real viewport sizes.
Start by reading the repo's existing UI patterns before designing anything new. Prefer established layout primitives, typography, spacing, navigation, form controls, loading states, empty states, error states, and test utilities over new visual systems.
Workflow
-
Map the user path.
- Identify the fewest practical clicks from entry point to successful outcome.
- Remove redundant confirmation screens, duplicate navigation, avoidable modals, and repeated data entry.
- Preserve necessary safety checks for destructive, billing, privacy, and admin actions.
-
Inventory existing patterns.
- Inspect similar pages and shared components before adding new layout or component styles.
- Reuse project design tokens, shells, grids, buttons, form fields, cards, menus, tabs, toasts, and table/list patterns.
- If a new pattern is required, make it small, explain why existing patterns do not fit, and keep it compatible with the current design language.
-
Design by actual viewport, not breakpoint labels.
- Reason about concrete widths and heights, including short laptop screens, tablet portrait/landscape, small phones, and wide desktop.
- Fill the useful viewport for primary tasks without creating empty "lg-only" layouts.
- Use grid, flex, container constraints,
minmax,min-height: 100dvh, sticky regions, and scroll regions intentionally. - Avoid viewport-scaled font sizing; make text responsive through layout, wrapping, hierarchy, and container constraints.
-
Keep every screen responsive.
- Verify no horizontal document overflow.
- Ensure long labels, names, emails, URLs, headings, and translated-length strings wrap or truncate intentionally.
- Ensure buttons, tabs, filters, table cells, cards, and form labels cannot resize the layout into overlap.
- Support keyboard navigation, focus visibility, touch targets, and accessible names.
What ships with it
3 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.
- 10d ago First seen · 72 lines · 88 tokens per session scan A f7fa8d157d5d
frontend-design-quality is a skill published in the GitHub repository jimtin/production-ai (1 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,012 once invoked, about $0.0004 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
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage…
frontend-specialist
A front-end development workflow for building or improving web pages, components, layouts, forms, dashboards, and responsive interfaces. It covers common tools and frameworks such as React, Vue, Next.js, Tailwind, and CSS.
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
awesome-design-md
Create a DESIGN.md style baseline BEFORE building UI. Use FIRST when no design draft exists — installs a proven visual style, then invoke frontend-design to implement. For borrowing a known product style, getting consistent typography/colors/spacing, or needing a fast visual starting point.
build-webgl-liquid-glass
Build production-ready GPU liquid-glass surfaces with liquid-gl for React or DOM UIs. Default for refractive cards, notifications, panels, GPU bevels, and WebGL glass.
build-sdf-liquid-glass
Build lightweight SDF/canvas displacement glass with Vaso. Use for responsive refractive cards, no-WebGL fallbacks, many compact surfaces, or explicit SDF requests.