frontend-design

A set of rules for building web pages, components, and applications with HTML, CSS, JavaScript, and related interface code.

In plain words
What is it for?
Use it when creating or improving a website interface, page layout, web component, or frontend application.
Why use it?
It gives frontend work consistent guidance for layout, typography, color, motion, interaction, and user-facing text. The input says it requires project and audience context before design work.

Skill for Claude CodeCodex

Part of the frontend-design plugin — 1 skill shipped together

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.

agentmods
npx agentmods add skills/harnessprotocol/harness-kit/frontend-design
Any agent
npx skills add harnessprotocol/harness-kit --skill frontend-design
Clone the repo
git clone --depth 1 https://github.com/harnessprotocol/harness-kit

Made for: Claude Code, Codex.

Or install frontend-design, the plugin that ships this one along with the rest of its 1 skill.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,380 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00068 $0.03380
Opus 5 $0.00034 $0.01690
Sonnet 5 $0.00014 $0.00676
Haiku 4.5 $0.00007 $0.00338

Measured 3d ago against content hash 91d5b00b08e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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.

plugins/frontend-design/skills/frontend-design/SKILL.md · 294 lines

How it starts

The opening of the file, as written. The whole thing — 294 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.

Context Gathering Protocol

Design without project context produces generic output. Before designing anything:

  1. Check for existing context: If your loaded instructions contain a Design Context section, use it.
  2. Ask if missing: You need at minimum — target audience, use cases, brand personality/tone. Code tells you what was built, not who it's for or what it should feel like. Ask before generating.

The AI Slop Test

Before shipping: "If someone saw this and said 'AI made this,' would they believe it immediately?"

If yes — fix it. The recurring fingerprints of AI-generated work:

  • Inter font, Roboto, Open Sans, Arial, or system defaults
  • Purple-to-blue gradients; cyan-on-dark; neon accents on dark backgrounds
  • Gray text on colored backgrounds
  • Glassmorphism used decoratively (blur cards, glow borders)
  • Pure black (#000) or pure white (#fff) anywhere
  • Everything wrapped in cards; cards nested inside cards; identical card grids
  • Everything centered; same spacing everywhere
  • Hero metric layout (big number, small label, supporting stats, gradient accent)
  • Dark mode as the default aesthetic (looks cool without requiring actual design decisions)
  • Gradient text for "impact" — decorative, not meaningful
  • Large rounded icons above every heading
  • Bounce / elastic easing
  • Sparklines as decoration
  • Rounded rectangles with generic drop shadows
  • ease as the default easing function

A distinctive interface makes someone ask "how was this made?" not "which AI made this?"

Design Direction

Commit to a bold, specific aesthetic direction before touching code:

  • 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. There are endless flavors. Design one true to the context, not a safe middle ground.
  • Differentiation: What's the one thing someone will remember?

Read the full file on GitHub · 294 lines

Files

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.

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. 3d ago First seen · 294 lines · 68 tokens per session scan A 91d5b00b08e9

Subscribe to this mod's changes

frontend-design is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 4d ago), licensed Apache-2.0. It adds 68 tokens to every session and 3,380 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-31.

Related

Other skills, from other repositories

kit-tailwind

Tailwind CSS guardrails pack — dynamic class purging, v4 CSS-first config, @apply/@reference, arbitrary values. Use when writing Tailwind utility classes or Tailwind configuration.

altafino/FableClaudeMDForOpus · 42 tokens

occupancy-calculator

Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.

AlpacaLabsLLC/skills-for-architects · 55 tokens

zoning-analysis-nyc

Analyze NYC lot zoning, FAR, height, setbacks, uses, and buildable envelope from PLUTO and the Zoning Resolution. Use for "what can I build"; use nyc-bsa for relief and zoning-envelope for 3D visualization.

AlpacaLabsLLC/skills-for-architects · 57 tokens

csv-to-sif

Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.

AlpacaLabsLLC/skills-for-architects · 38 tokens

epd-parser

Extract GWP, life-cycle stages, certifications, and impact metrics from an EPD PDF. Use when given a declaration to parse; not to find or compare EPDs.

AlpacaLabsLLC/skills-for-architects · 40 tokens

meeting-minutes

Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…

AlpacaLabsLLC/skills-for-architects · 72 tokens