agentleFS
krivooxkrivoox/agent-stack-template/.cursor/rules/performance.mdc

agent-stack-template / rules

Cursor rule31 starsChanged 3 months agoMITView on GitHub

Navigation, caching and PWA contract

The file

We split this performance.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every (app) segment ships a loading.tsx built on PageSkeleton.

    line 15
  2. Very specific:

    After a mutation, use refreshAfterMutation / navigateAndRefresh from src/lib/navigation.ts.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
performance.mdc
---
description: Navigation, caching and PWA contract
globs: src/app/**/*.tsx,src/app/**/*.ts,next.config.ts,src/components/app-shell/**/*.ts,src/components/app-shell/**/*.tsx
alwaysApply: false
---

# Performance and navigation

Detail: `docs/architecture.md` §7.

## Required

1. Soft navigation only. The shell in `(app)/layout.tsx` is persistent; a full
   page reload during an authenticated session is a bug.
2. Every `(app)` segment ships a `loading.tsx` built on `PageSkeleton`.
3. `experimental.staleTimes.dynamic: 0`. Perceived speed comes from skeletons
   and prefetch, not from showing data captured before the last mutation.
4. Nav destinations live in `nav-config.ts` so idle prefetch covers them.
5. After a mutation, use `refreshAfterMutation` / `navigateAndRefresh` from
   `src/lib/navigation.ts`. A plain `router.push` can land on a Client Router
   Cache entry captured before the write.
6. Authenticated routes are `private, no-store` — add the prefix to
   `PRIVATE_ROUTE_PREFIXES` in `next.config.ts`.

## Forbidden

- Cross-request caching of tenant data (balances, membership, anything
  per-user).
- A service worker that caches HTML or `/api/*`. Static assets under
  `/_next/static/*` only — they are content-hashed and immutable.
- Offline UI that displays stale authoritative data. Users trust what they see;
  a stale number is worse than no number.
- Relaxing `staleTimes.dynamic` to make a page feel faster.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.