What is frontend-architecture?

A set of rules for structuring Vite and React single-page applications, including routes, pages, shared components, data requests, configuration, and code splitting.

Use it to decide where to place route shells, lazy-loaded screens, components, hooks, services, configuration, and shared data-transfer schemas in a React application.

It gives related frontend code predictable locations and keeps routing, server data, shared UI, and feature code connected without unnecessary duplication.

frontend-architecture — Cursor rule for Cursor by louisbrulenaudet

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/louisbrulenaudet/monorepo-template

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/frontend-architecture/github.svg)](https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/frontend-architecture)

Your own site

<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/frontend-architecture"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/frontend-architecture/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/frontend-architecture"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/frontend-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,469 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01469
Opus 5	$0.00000	$0.00734
Sonnet 5	$0.00000	$0.00294
Haiku 4.5	$0.00000	$0.00147

Measured 10d ago against content hash 304c434b4092, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

frontend-architecture 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 10d 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.

.cursor/rules/frontend/frontend-architecture.mdc · 50 lines

How it starts

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

Frontend Architecture (Vite + React) Rules

Cross-cutting scaffolding for the React SPAs. Component/hook authoring is in react.mdc; server state in tanstack-query.mdc; routing in tanstack-router.mdc. This file is the wiring between them.

Directory layout

Thin route shells under src/routes/ (file-based - see tanstack-router.mdc) hold loaders, guards, and search validation; the code-split UI entry is the paired src/routes/*.lazy.tsx, and the actual screen lives in src/pages/ (imported by the lazy route). Shared UI sits in src/components/ (with primitives in src/components/ui/); non-render logic in src/hooks/, src/services/, src/utils/; frontend-only enums in src/enums/; runtime config in src/config/ (env.ts, query-client.ts).
HTTP calls and their queryOptions live together under src/services/worker-api/ (<feature>.ts + <feature>-query-options.ts). Wire schemas are not redefined here - they come from @repo/dtos-common.
Colocate feature code (route + its queries + its components) over deep global folders. Use package.json "imports" (#/* → ./src/*) for in-app absolute imports (e.g. #/components/ui/Button); see vite-config.mdc and the TypeScript config rule.
Filenames stay kebab-case; a React component file may be PascalCase to mirror its export. See naming.mdc.

Vite config

When editing vite.config.ts, follow vite-config.mdc - plugin order, Rolldown/Oxc build options, monorepo fs.allow, env guards, and generated dist/_headers.
Hook rules (react/rules-of-hooks, react/exhaustive-deps) are enforced by oxlint, not ESLint - they are configured for apps/front-*/src/** in .oxlintrc.json. Do not add an ESLint/eslint-plugin-react-hooks toolchain; pnpm run ci runs oxlint.

Cloudflare Workers deployment

These SPAs deploy as static assets + SPA routing on Cloudflare Workers - @cloudflare/vite-plugin in vite.config.ts, deploy settings in wrangler.jsonc. Router/query devtools stay dev-only (see below).
Keep the Vite plugin assets-only for front-*. Never add auxiliaryWorkers to pull in worker-api, and never co-locate gateway/API routes in the SPA Worker. SPA to gateway remains HTTP only; worker-api stays on Wrangler.

Read the full file on GitHub · 50 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.

10d ago First seen · 50 lines · 0 tokens per session scan A 304c434b4092

Subscribe to this mod's changes

frontend-architecture is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,469 tokens. 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.

CSS and styling Claude Code Frontend React agent ai-agents cloudflare cloudflare-workers cursor

frontend-architecture

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Frontend Architecture (Vite + React) Rules

Directory layout

Vite config

Cloudflare Workers deployment

What this file has done since we first saw it

Other cursor rules, from other repositories

cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup

nextjs-react-tailwind-cursorrules-prompt-file

python-fastapi-scalable-api-cursorrules-prompt-fil

nextjs-material-ui-tailwind-css-cursorrules-prompt

react-components-creation-cursorrules-prompt-file

react-chakra-ui-cursorrules-prompt-file