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/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/franrom/pupila/frontend-design"><img src="https://agentmods.dev/badge/skills/franrom/pupila/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.00077 | $0.00616 |
| Opus 5.5 | $0.00031 | $0.00246 |
| Sonnet 5.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 1mo 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.
- 1mo 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 yesterday), licensed MIT. It adds 77 tokens to every session and 616 once invoked, about $0.0003 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-30.
Other skills, from other repositories
styling-sidebar-products
How products and pages appear in the PostHog sidebar: which category they sit in, which icon and color they get, and which groups share a color gradient. Use when adding a product or data management page to the sidebar (treeItemsProducts or treeItemsMetadata in a products//manifest.tsx), giving an entry a new icon or…
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…
elements
Use this skill by default for any UI-related work or with NVIDIA Elements (nve-), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.
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.