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 int2t05/engineering-skills --skill frontend-designgit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/int2t05/engineering-skills/frontend-design)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/frontend-design"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/frontend-design/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/int2t05/engineering-skills/frontend-design"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/frontend-design.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.00024 | $0.01009 |
| Opus 5.5 | $0.00010 | $0.00404 |
| Sonnet 5.5 | $0.00005 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
frontend-design 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
When to use
- Design or improve an interface and validate its rendered behavior.
Not for: image-to-code for reference fidelity; design-research for existing visuals.
Steps
-
Identify users, core flow, design system, framework and viewports; do not fabricate personas or usability results.
-
Define hierarchy, layout, typography, spacing and color from the brief and existing system rather than universal color formulas.
-
Specify relevant loading, empty, error, focus, disabled and success states, keyboard access and responsive behavior.
-
Implement when authorized, run the interface and inspect screenshots and interactions; create a design report only when its consumer and path are agreed.
Output: Suggested paths, subject to human audit: docs/design/DESIGN.md, docs/design/frontend-audit.md or docs/research/ux-research.md only for corresponding requested work.
Verify
- Critical flows work at target viewports and with keyboard input; visual claims use actual renders.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- design-principles.md — design discipline (CRAP, hierarchy before decoration, minimize cognitive load, design every state, accessibility non-optional, consistency from systems)
- human-audit.md — document consent, readability and human review.
- product-icon.md — generating a product icon / favicon as SVG (mature brand references, restrained geometry and small-size checks)
- references/styles.md — 21 UI styles with effect specs (shadows, blur, radius)
- references/palettes.md — 12 palette directions by product type
- references/font-pairings.md — 31 font pairings across 10 personality categories
- references/ux-guidelines.md — 232 UX guidelines across 10 priority categories + pre-delivery checklist
- references/apple-hig.md — Apple HIG routing table + quick-reference specs
- references/brief-inference.md — design-read protocol + 3 dials (variance, motion, density) + design-system selection map
- references/anti-tells.md — forbidden AI patterns + pre-flight check matrix
- references/motion-system.md — motion token scale, easing catalog, choreography patterns, scroll-animation skeletons
- references/design-tokens.md — token tiers, naming convention, scales (spacing, radius, elevation, z-index)
- references/component-anatomy.md — compound components, slot architecture, variant axes, composition patterns
- references/state-management.md — client vs server state, store/cache selection, state machines, optimistic updates, derived state, normalization
- references/design-foundations.md — design theory in one place: Perception & Gestalt, Cognitive Laws (Hick's, Fitts's, Miller, Tesler, Von Restorff), Color (HSB, schemes, 70:25:5), Typography (anatomy, rhythm, scale), Hierarchy & Layout (F/Z patterns, squint/5-second tests, CRAP), Usability Heuristics (Nielsen 10, Norman, Rams), Information Architecture (4 elements, card sorting, labeling)
- references/state-design.md — four states (loading/error/empty/partial), skeleton screens, empty-state design, error recovery
- references/material-design.md — Material 3 color/type/elevation/state-layer roles, M3 vs M2, when Material vs HIG vs custom
- references/ux-research.md — user interviews, personas, journey maps, empathy maps, usability testing (5-user rule, think-aloud)
- references/visual-direction.md — shared web visual-direction engine for imagegen (web mode) and image-to-code (variation axes, hero scale, composition anchors, anti-slop)
- references/design-system-audit.md — token coverage vs hardcoded values audit, component variant/state/a11y documentation, systematic extension patterns
What ships with it
18 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.
- agents/openai.yaml 128 B
- references/anti-tells.md 7.6 KB
- references/apple-hig.md 9.6 KB
- references/brief-inference.md 6.4 KB
- references/component-anatomy.md 6.0 KB
- references/design-foundations.md 32 KB
- references/design-system-audit.md 5.9 KB
- references/design-tokens.md 6.2 KB
- references/font-pairings.md 6.1 KB
- references/material-design.md 7.0 KB
- references/motion-system.md 7.2 KB
- references/palettes.md 6.4 KB
- references/state-design.md 6.2 KB
- references/state-management.md 6.4 KB
- references/styles.md 12 KB
- references/ux-guidelines.md 28 KB
- references/ux-research.md 8.5 KB
- references/visual-direction.md 8.2 KB
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 Changed · -98 lines · -42 tokens per session d4626cf2280c
- 16d ago Changed · +2 lines c8b96d54d494
- 1mo ago Changed · +1 lines 80f19277462b
- 1mo ago First seen · 148 lines · 66 tokens per session scan A 738394eebdf4
frontend-design is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 1,009 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-08-31.
Other skills, from other repositories
design-reviewer
Use after AC and before RED for any wave that ships UI. Performs component API audit against installed dist files, produces per-route mockup, defines visual ACs, flags design-system gaps. Output written to .wave/dr.md.
nw-fp-usable-design
Naming conventions, API ergonomics, and usability patterns for functional code.
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.