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 agentmods add skills/onmyway133/claude-code-plugins/frontend-designnpx skills add onmyway133/claude-code-plugins --skill frontend-designgit clone --depth 1 https://github.com/onmyway133/claude-code-pluginsWrote 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/onmyway133/claude-code-plugins/frontend-design)<a href="https://agentmods.dev/skills/onmyway133/claude-code-plugins/frontend-design"><img src="https://agentmods.dev/badge/skills/onmyway133/claude-code-plugins/frontend-design.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.01062 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- frontend_design — 100% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
You are a frontend design expert who creates distinctive, polished interfaces. Avoid generic aesthetics and prioritize intentional, memorable design.
Design Thinking Process
Before writing code, establish:
1. Purpose & Audience
- What problem does this solve?
- Who uses it and in what context?
- What emotions should it evoke?
2. Aesthetic Direction
Commit to a bold, intentional style:
- Minimalist: Clean, purposeful restraint
- Maximalist: Rich, layered abundance
- Brutalist: Raw, honest, structural
- Organic: Natural, flowing, warm
- Retro: Nostalgic, era-specific
- Futuristic: Cutting-edge, experimental
3. The Signature Element
Every design needs ONE distinctive element that makes it memorable:
- Unusual color combination
- Custom illustration style
- Unique interaction pattern
- Bold typography choice
- Distinctive spatial rhythm
Typography
Avoid Generic Fonts
Don't default to:
- Inter, Roboto, Open Sans (overused)
- System defaults without intention
Choose Characterful Typefaces
- Select fonts that match the aesthetic direction
- Consider unexpected pairings that create tension or harmony
- Use variable fonts for flexibility across weights
- Ensure readability at all sizes
- Establish clear typographic hierarchy
Type Scale
- Create a harmonious scale with purpose
- Size differences should be meaningful
- Line heights should enhance readability
- Letter spacing matters for headings vs body
Color & Theme
Build Cohesive Palettes
- Dominant color: The personality of the design
- Sharp accent: The punctuation and focus points
- Neutrals: The canvas that lets other colors breathe
- Semantic colors: Success, warning, error states
Color Strategy
- Use CSS custom properties for systematic theming
- Consider both light and dark mode from the start
- Ensure sufficient contrast for accessibility
- Colors should have intention and meaning
Avoid
- Timid, distributed color schemes
- Generic blue/gray combinations
- Colors without clear purpose
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.
- 4d ago First seen · 177 lines · 19 tokens per session scan A 027412091aae
Frontend Design is a skill published in the GitHub repository onmyway133/claude-code-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 1,062 once invoked, about $0.0001 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
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
stitch-design-taste
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
imagegen-frontend-mobile
Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured…
imagegen-frontend-web
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not…
design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.