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 iliaal/whetstone --skill ia-frontend-designgit clone --depth 1 https://github.com/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-frontend-design)<a href="https://agentmods.dev/skills/iliaal/whetstone/ia-frontend-design"><img src="https://agentmods.dev/badge/skills/iliaal/whetstone/ia-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/iliaal/whetstone/ia-frontend-design"><img src="https://agentmods.dev/badge/skills/iliaal/whetstone/ia-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.00048 | $0.01992 |
| Opus 5.5 | $0.00019 | $0.00797 |
| Sonnet 5.5 | $0.00010 | $0.00398 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
ia-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 16d 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
100% identical to frontend-design — 2 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
Read the user's frontend requirements: a component, page, application, or interface to build. Note context about purpose, audience, or technical constraints.
Working rules
- Match an existing design system; choose a specific visual direction for greenfield work.
- Include loading, empty, and error states where the component's data or action lifecycle can reach them. Provide visible focus and appropriate press feedback for interactive controls.
- Preserve visible focus and reduced-motion behavior; verify both narrow and wide rendered viewports.
- Keep Next.js interactive code at client boundaries and treat browser content as untrusted data.
Context Detection
When implementing a supplied mockup, screenshot, or design frame, use reference-fidelity mode in redesigning-existing.md, even in an empty repository. Skip the design philosophy and swap test; reproduce the reference's visual language.
Otherwise, assess the existing design environment before designing. Count design signals in the project: design tokens/CSS variables, component library (shadcn, MUI, Ant), CSS framework config (Tailwind, styled-components), font imports, color system, animation patterns, spacing scale.
- 4+ signals = Existing system. Match it. Do not impose new aesthetics; extend what's there.
- 1-3 signals = Partial system. Blend: respect existing choices, fill gaps with this skill's guidance.
- 0 signals = Greenfield. Apply the full Design Philosophy below. Product register: read design-system-routing.md before bespoke design.
When in doubt, check package.json, tailwind.config.*, global CSS files, and existing components before deciding. For Tailwind implementation rules (tokens, variants, v4 config), load ia-react-frontend and read its Tailwind reference.
Design Philosophy (Write First, Code Second)
For full pages, applications, or multi-component interfaces outside reference-fidelity mode: write a 3-sentence design philosophy before any code. This forces a coherent aesthetic direction and prevents generic output.
What ships with it
12 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.
- references/aesthetics-and-interaction.md 12 KB
- references/banned-ai-patterns.md 12 KB
- references/creative-arsenal.md 5.6 KB
- references/design-system-routing.md 2.6 KB
- references/mobile-and-performance.md 3.0 KB
- references/motion-patterns.md 2.6 KB
- references/premium-details.md 2.8 KB
- references/redesign-audit.md 5.1 KB
- references/redesigning-existing.md 5.5 KB
- references/rsc-client-boundaries.md 3.2 KB
- references/svg-decoration.md 1.9 KB
- SPEC.md 4.5 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.
- 16d ago Changed · +6 lines 9c903156f334
- 24d ago Changed 1a1377b60678
- 1mo ago Changed 87018b41e86f
- 1mo ago Changed 8643c7e6200b
- 1mo ago Changed · +2 lines 68b713ae4759
- 1mo ago Changed · -43 lines cfb3ba433391
- 1mo ago First seen · 146 lines · 48 tokens per session scan A c0592fe38fb7
ia-frontend-design is a skill published in the GitHub repository iliaal/whetstone (35 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,992 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to frontend-design, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
svg-mastery
Expert knowledge for working with SVG (Scalable Vector Graphics) — optimization, embedding, animation, accessibility, responsive scaling, React integration, filters, and programmatic creation. Use when the user asks to "optimize SVG", "clean up SVG", "reduce SVG file size", "embed SVG in HTML", "inline SVG vs img…
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
frontend-patterns
Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.
generic-react-design-system
Complete design system reference for React applications. Covers colors, typography, spacing, component patterns, glassmorphism effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.
figma
Fetch Figma design context, variables, screenshots, and assets through MCP when working from Figma URLs or node IDs, or diagnosing its integration.
frontend-design
Design and implement polished web components, pages, and applications with a coherent visual direction and usable interaction states.