frontend-design

frontend-design is a cursor rule for Cursor from thatrebeccarae/claude-marketing. It costs 55 tokens per session (3,982 once invoked), scanned A, original, MIT.

A set of guidelines for designing and building distinctive web interfaces with HTML, CSS, JavaScript, or React. It covers layout, typography, colors, animation, accessibility, and code quality.

In plain words
What is it for?
Use it to create or improve production web pages and React interfaces, including their visual style, responsive layout, motion, and implementation quality.
Why use it?
It helps avoid generic-looking interfaces by requiring a clear visual direction and decisions suited to the product and its users. It also connects the visual design to working frontend code.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to create or improve production web pages and React interfaces, including their visual style, responsive layout, motion, and implementation quality.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/thatrebeccarae/claude-marketing/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.

Clone the repo
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing

Made for: Cursor.

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/rules/thatrebeccarae/claude-marketing/frontend-design.svg)](https://agentmods.dev/rules/thatrebeccarae/claude-marketing/frontend-design)
Your own site
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/frontend-design"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/frontend-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,982 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 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.00055 $0.03982
Opus 5 $0.00028 $0.01991
Sonnet 5 $0.00011 $0.00796
Haiku 4.5 $0.00006 $0.00398

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

integrations/cursor/frontend-design.mdc · 486 lines

How it starts

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

Frontend Design

Create distinctive, production-grade web interfaces that avoid generic AI aesthetics.

Design Thinking Process

1. Understand Context

Before writing code, answer:

  • Purpose: What problem does this interface solve? Who uses it?
  • Audience: Technical sophistication, expectations, emotional state when arriving
  • Constraints: Framework requirements, browser support, performance budget, accessibility needs

2. Commit to an Aesthetic Direction

Choose a specific point of view — not "clean and modern" but a real aesthetic:

Direction Characteristics
Brutally minimal Monochrome, system fonts, stark spacing, no decoration
Maximalist Dense, layered, multiple type scales, rich texture
Retro-futuristic Neon accents, dark backgrounds, grid lines, monospace
Organic/natural Soft shapes, earth tones, hand-drawn elements, warm
Luxury/refined Thin serifs, generous whitespace, muted palette, restrained
Playful/toy-like Rounded shapes, bright primaries, bouncy animations
Editorial/magazine Strong grid, dramatic type hierarchy, pull quotes
Brutalist/raw Exposed structure, monospace, raw HTML feeling
Art deco/geometric Symmetry, metallic accents, decorative borders, angular
Soft/pastel Light palette, gentle gradients, rounded, approachable
Industrial/utilitarian Exposed grid, status indicators, dense information

3. Identify the Memorable Thing

Every interface should have one element someone remembers:

  • An unexpected interaction
  • A distinctive type treatment
  • A bold color choice
  • An animation that surprises
  • A layout that breaks convention

4. Execute with Intentionality

The key is commitment, not intensity. Maximalism executed fully works. Minimalism executed with precision works. The mushy middle does not.

Typography

Principles

  • Choose distinctive fonts, NOT defaults (avoid Arial, Inter, Roboto for display use)
  • Pair a display font (personality) with a body font (readability)
  • Size hierarchy: display (48-96px), heading (24-36px), body (16-18px), small (12-14px)
  • Tight letter-spacing on large display text (-0.02 to -0.04em)
  • Normal or slightly loose spacing on body text

Read the full file on GitHub · 486 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. 8d ago First seen · 486 lines · 55 tokens per session scan A 851fb1b73ce9

Subscribe to this mod's changes

frontend-design is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (132 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 3,982 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.