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.
git clone --depth 1 https://github.com/gracefullight/docusaurus-pluginsWrote 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.
[](https://agentmods.dev/rules/gracefullight/docusaurus-plugins/frontend)<a href="https://agentmods.dev/rules/gracefullight/docusaurus-plugins/frontend"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/frontend/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.
<a href="https://agentmods.dev/rules/gracefullight/docusaurus-plugins/frontend"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01517 |
| Opus 5.5 | $0.00000 | $0.00607 |
| Sonnet 5.5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00152 |
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 1mo 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.
This is a copy
94% identical to frontend — 13 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Coding Standards
Core Rules
- Component Reuse: Use
shadcn/uicomponents first. Extend viacvavariants or composition. Avoid custom CSS. - Design Fidelity: Code must map 1:1 to
DESIGN.md(Section 9 — Agent Prompt Guide) and Design Tokens. Resolve discrepancies before implementation. - Rendering Strategy: Default to Server Components for performance. Use Client Components only for interactivity and API integration.
- Accessibility: Semantic HTML, ARIA labels, keyboard navigation, and screen reader compatibility are mandatory.
- Tool First: Check for existing solutions and tools before coding.
- Proxy over Middleware (BANNED): Next.js 16+ uses
proxy.tsfor request proxying.middleware.tsis NOT "deprecated" — it is forbidden in this project, touch it and you die. Do NOT create, recommend, suggest, or "restore"middleware.ts. Do NOT flagproxy.tsas dead code, unused, or not-wired. Do NOT demand a rename tomiddleware.ts. Any such finding is a fatal self-error — retract it immediately and writeproxy.ts. - No Prop Drilling: Avoid passing props beyond 3 levels. Use Jotai atoms instead. Avoid React Context.
- Auth Boundary: Frontend handles auth UI and token storage only. Never import database adapters, ORMs, or server-side auth libraries.
- Animation Library: Use
motion(import frommotion/react).framer-motionis the legacy package name and is BANNED — neverimport { motion } from 'framer-motion', never addframer-motiontopackage.json. Add themotionpackage via the project's package manager — detect from the lockfile (bun.lock→ bun,pnpm-lock.yaml→ pnpm,yarn.lock→ yarn,package-lock.json→ npm); default tobunwhen no lockfile exists. Import asimport { motion, AnimatePresence } from 'motion/react'. Respectprefers-reduced-motionviauseReducedMotionfrommotion/react. - Framework Version:
next@16+andreact@19+are MANDATORY. When scaffolding or pinningpackage.json, set"next": "^16"(or higher) and"react": "^19"/"react-dom": "^19"— never pinnextto^15,~15, or any range whose floor is below16.0.0. Ifcreate-next-app(or any scaffold tool) producesnext < 16, immediately bump it before committing. This rule is paired with Core Rule #6 (proxy.ts), which assumes Next.js 16+.
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.
- 1mo ago First seen · 81 lines · 0 tokens per session scan A aa4f02355c74
frontend is a cursor rule published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,517 tokens. A static security scan graded it A with 0 findings. It is 94% identical to frontend, differing in 13 lines, and is treated as a copy.
Other cursor rules, from other repositories
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.