frontend-design

frontend-design is a skill for Claude Code from RashadAnsari/myagents. It costs 43 tokens per session (815 once invoked), scanned A, a copy of frontend-design, MIT.

A design guide for building distinctive, production-ready web pages, components, and applications.

In plain words
What is it for?
It is for planning and implementing frontend interfaces by choosing a clear visual direction, considering users and constraints, and adding memorable design details.
Why use it?
It helps developers make interfaces that are visually deliberate and usable instead of relying on generic layouts or styling.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the albino plugin — 8 skills, 10 commands, 14 agents, 3 MCP servers shipped together

Good fit It is for planning and implementing frontend interfaces by choosing a clear visual direction, considering users and constraints, and adding memorable design details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rashadansari/myagents/frontend-design
Install

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.

Any agent
npx skills add RashadAnsari/myagents --skill frontend-design
Clone the repo
git clone --depth 1 https://github.com/RashadAnsari/myagents

Made for: Claude Code.

Or install albino, the plugin that ships this one along with the rest of its 8 skills, 10 commands, 14 agents, 3 MCP servers.

Wrote 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.

agentmods badge for frontend-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/rashadansari/myagents/frontend-design/github.svg)](https://agentmods.dev/skills/rashadansari/myagents/frontend-design)
Your own site
<a href="https://agentmods.dev/skills/rashadansari/myagents/frontend-design"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/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.

agentmods 80×15 button for frontend-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/rashadansari/myagents/frontend-design"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/frontend-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 815 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00815
Opus 5 $0.00022 $0.00407
Sonnet 5 $0.00009 $0.00163
Haiku 4.5 $0.00004 $0.00081

Measured 10d ago against content hash 8cd2c6dd0b7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

Origin

This is a copy

91% identical to frontend-design — 3 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.

plugins/albino/skills/frontend-design/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.

Design Thinking

Before coding, understand the context and commit to a BOLD aesthetic direction:

  • Purpose: What problem does this interface solve? Who uses it?
  • Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
  • Constraints: Technical requirements (framework, performance, accessibility).
  • Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?

CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.

Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:

  • Production-grade and functional
  • Visually striking and memorable
  • Cohesive with a clear aesthetic point-of-view
  • Meticulously refined in every detail

Frontend Aesthetics Guidelines

Focus on:

  • Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
  • Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
  • Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
  • Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
  • Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 10d ago First seen · 42 lines · 43 tokens per session scan A 8cd2c6dd0b7d

Subscribe to this mod's changes

frontend-design is a skill published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 815 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to frontend-design, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…

wshobson/agents · 112 tokens

wcag-audit-patterns

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

wshobson/agents · 45 tokens

sag

ElevenLabs text-to-speech with mac-style say UX.

SafeAI-Lab-X/ClawKeeper · 16 tokens

pn-animation

Motion philosophy and governance for web interfaces. Covers the motion role taxonomy (Reveal/Orient/Confirm/Delight), library selection guide, motion budgets by page mode, prefers-reduced-motion compliance, and motion map output format. Use when designing a motion system, auditing animations, or choosing libraries.…

perniemann/pnCore · 82 tokens

pn-color-system

Color system design and implementation: OKLCH color space, tinted neutrals, palette structure, contrast, dark mode architecture, and token hierarchy. Use when establishing color tokens, theming, dark mode, or reviewing color choices.

perniemann/pnCore · 50 tokens

pn-design-system

Establishes or maintains a design system: tokens, CSS variables, spacing/type scales, theming, and consistency auditing. Use when defining tokens or auditing components. The pn-design-system rule enforces token usage when editing CSS/SCSS files.

perniemann/pnCore · 54 tokens