Borrowing it
Nothing to install: this file belongs to FranRom/pupila. 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/FranRom/pupila/main/.agents/skills/frontend-design/SKILL.mdgit clone --depth 1 https://github.com/FranRom/pupilaWrote 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/franrom/pupila/frontend-design)<a href="https://agentmods.dev/skills/franrom/pupila/frontend-design"><img src="https://agentmods.dev/badge/skills/franrom/pupila/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.1 | $0.00077 | $0.00616 |
| Opus 5 | $0.00039 | $0.00308 |
| Sonnet 5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00062 |
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 7d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guides distinctive, production-grade frontend. Avoid generic "AI slop". Ship working code. Obsess details.
User supplies requirements: component, page, app, interface. May include purpose, audience, tech constraints.
Design Thinking
Before code, commit to BOLD direction:
- Purpose: Problem? User?
- Tone: Pick extreme — brutally minimal, maximalist chaos, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, pastel, industrial. Inspiration only — design true to chosen direction.
- Constraints: Framework, perf, a11y.
- Differentiation: UNFORGETTABLE hook? One memorable thing?
CRITICAL: Pick clear conceptual direction, execute precisely. Bold maximalism and refined minimalism both work — intentionality matters, not intensity.
Implement code (HTML/CSS/JS, React, Vue, etc.):
- Production-grade, functional
- Visually striking, memorable
- Cohesive POV
- Refined details
Frontend Aesthetics Guidelines
Focus:
- Typography: Beautiful, unique fonts. Skip Arial/Inter. Pick characterful. Pair distinctive display + refined body.
- Color & Theme: Cohesive aesthetic. CSS vars. Dominant colors + sharp accents beat timid even palettes.
- Motion: Animations + micro-interactions. CSS-only for HTML. Motion lib for React. High-impact moments: one orchestrated page load w/ staggered reveals (animation-delay) > scattered micro-interactions. Scroll triggers, surprise hovers.
- Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking. Negative space OR controlled density.
- Backgrounds & Visual Details: Atmosphere, depth — not flat color. Contextual effects, textures matching aesthetic. Gradient meshes, noise, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, grain.
NEVER: Inter, Roboto, Arial, system fonts, purple-gradient-on-white, predictable layouts, cookie-cutter patterns.
Make unexpected choices fitting context. Vary themes (light/dark), fonts, aesthetics. NEVER converge on common picks (e.g. Space Grotesk) across generations.
What ships with it
1 file 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.
- 7d ago First seen · 43 lines · 77 tokens per session scan A d80cab9a2604
frontend-design is a skill published in the GitHub repository FranRom/pupila (36 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 616 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-30.
Other skills, from other repositories
omh-frontend
This is a Hermes-native frontend workflow skill.
omh-visual-qa
This is a Hermes-native visual-qa workflow skill.
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.