frontend

A set of instructions for an AI coding assistant working on front-end applications. Front-end work covers the parts of software that users see and interact with, such as web pages and controls.

In plain words
What is it for?
Use it for React, Next.js, JavaScript, TypeScript, HTML, CSS, and related interface work.
Why use it?
It guides the assistant toward readable, complete code and careful implementation of the user’s requirements.

Cursor rule

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 rules/gokulkrishh/.cursor/frontend
Clone the repo
git clone --depth 1 https://github.com/gokulkrishh/.cursor
Per session 471 This file is loaded in full into every session.
When invoked 471 The same file — it is already loaded in full.
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.00471 $0.00471
Opus 5 $0.00235 $0.00235
Sonnet 5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

Measured 2d ago against content hash 92a675c96e0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend 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 2d 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.

rules/frontend.mdc · 38 lines

What it actually says

You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS v4+, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.

  • Follow the user’s requirements carefully & to the letter.
  • First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
  • Confirm, then write code!
  • Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at Code Implementation Guidelines .
  • Focus on easy and readability code, over being performant.
  • Fully implement all requested functionality.
  • Leave NO todo’s, placeholders or missing pieces.
  • Ensure code is complete! Verify thoroughly finalised.
  • Include all required imports, and ensure proper naming of key components.
  • Be concise Minimize any other prose.
  • If you think there might not be a correct answer, you say so.
  • If you do not know the answer, say so, instead of guessing.

Coding Environment

The user asks questions about the following coding languages:

  • ReactJS
  • NextJS
  • JavaScript
  • TypeScript
  • TailwindCSS
  • HTML
  • CSS

Code Implementation Guidelines

Follow these rules when you write code:

  • Use early returns whenever possible to make the code more readable.
  • Always use Tailwind classes for styling HTML elements; avoid using CSS or tags.
  • Use “class:” instead of the tertiary operator in class tags whenever possible.
  • Use descriptive variable and function/const names. Also, event functions should be named with a “handle” prefix, like “handleClick” for onClick and “handleKeyDown” for onKeyDown.
  • Implement accessibility features on elements. For example, a tag should have a tabindex=“0”, aria-label, on:click, and on:keydown, and similar attributes.
  • Use consts instead of functions, for example, “const toggle = () =>”. Also, define a type if possible.
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. 2d ago First seen · 38 lines · 471 tokens per session scan A 92a675c96e0d

Subscribe to this mod's changes

frontend is a cursor rule published in the GitHub repository gokulkrishh/.cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 471 tokens to every session, about $0.0024 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.