awesome-agv: Skill for Claude Code

.agents/skills/frontend-design/SKILL.md

frontend-design is a skill for Claude Code, Codex from irahardianto/awesome-agv. It costs 67 tokens per session (2,241 once invoked), scanned A, original, MIT.

A design guide for creating polished frontend interfaces in React, Vue, or plain HTML and CSS, with a deliberate visual direction, typography, color choices, and motion.

In plain words
What is it for?
Use it when building or restyling websites, landing pages, dashboards, posters, and other frontend screens.
Why use it?
It helps avoid repetitive-looking interfaces by requiring design decisions before implementation and providing reference material for those choices.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is irahardianto/awesome-agv's own configuration. It tells Claude Code and Codex how to work on awesome-agv itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything awesome-agv configures →

Reuse

Borrowing it

Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/skills/frontend-design/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/irahardianto/awesome-agv

Made for: Claude Code, Codex.

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/irahardianto/awesome-agv/frontend-design/github.svg)](https://agentmods.dev/skills/irahardianto/awesome-agv/frontend-design)
Your own site
<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/frontend-design"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/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/irahardianto/awesome-agv/frontend-design"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/frontend-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,241 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00067 $0.02241
Opus 5 $0.00034 $0.01120
Sonnet 5 $0.00013 $0.00448
Haiku 4.5 $0.00007 $0.00224

Measured 11d ago against content hash d4479f0d6ac1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/visual-audit.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/frontend-design/SKILL.md · 175 lines

How it starts

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

Frontend Design Skill

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Follow the phased workflow below. Each phase has concrete reference material — use it, don't invent from scratch.


Phased Workflow

Phase 1: Design Direction

Before touching any code, commit to a clear aesthetic direction. Answer these:

Context questions:

  • What problem does this interface solve? Who uses it?
  • What's the one thing someone will remember about this design?
  • What aesthetic direction fits? (Choose ONE — don't blend randomly)

Aesthetic directions to pick from: Brutally minimal · Maximalist chaos · Retro-futuristic · Organic/natural · Luxury/refined · Playful/toy-like · Editorial/magazine · Brutalist/raw · Art deco/geometric · Soft/pastel · Industrial/utilitarian · Sci-fi/cyberpunk

CRITICAL: Every generation must make a fresh choice. Never default to the same direction twice. Vary light/dark themes, fonts, and palettes across generations.

Deliverables from Phase 1:

  • ✓ Named aesthetic direction (e.g., "editorial luxury, dark theme")
  • ✓ Font pairing selected from references/typography.md
  • ✓ Color palette selected from references/color-palettes.md
  • ✓ Layout composition(s) selected from references/layout-compositions.md

Phase 2: Token System

Set up the design token foundation before writing any component code.

  1. Copy examples/design-tokens.css into the project
  2. Override the palette primitives with your chosen palette's HSL values
  3. Override --font-display and --font-body with your chosen font pairing
  4. Add the Google Fonts @import to your HTML <head> (with preconnect hints)
<!-- Always preconnect BEFORE the font stylesheet -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link rel="stylesheet" href="[your @import from typography.md]">

Deliverables from Phase 2:

  • design-tokens.css (or equivalent) in place with chosen palette/fonts
  • ✓ All colors, spacing, typography, shadows, and motion defined as CSS variables
  • ✓ No hardcoded color values or magic numbers anywhere in component code

Read the full file on GitHub · 175 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. 11d ago First seen · 175 lines · 67 tokens per session scan A d4479f0d6ac1

Subscribe to this mod's changes

frontend-design is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 20d ago), licensed MIT. It adds 67 tokens to every session and 2,241 once invoked, about $0.0003 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.