performance

performance is a cursor rule for Cursor from vibestackdev/vibe-stack. It costs 0 tokens per session (561 once invoked), scanned A, original, MIT.

A set of Next.js rules for making web pages load faster, including guidance on data fetching, caching, JavaScript bundle size, and Core Web Vitals, which are Google's measures of user-perceived page performance.

In plain words
What is it for?
Use it when building or reviewing Next.js pages, server data fetching, cached computations, dynamic imports, and client components.
Why use it?
It helps avoid slow data requests, repeated database queries, oversized browser downloads, and other common performance problems.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when building or reviewing Next.js pages, server data fetching, cached computations, dynamic imports, and client components.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/vibestackdev/vibe-stack/performance
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/vibestackdev/vibe-stack

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 performance

README.md
[![agentmods](https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/performance/github.svg)](https://agentmods.dev/rules/vibestackdev/vibe-stack/performance)
Your own site
<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/performance"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/performance/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.

agentmods 80×15 button for performance

Your own site · 80×15
<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/performance"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/performance.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 561 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.00000 $0.00561
Opus 5.5 $0.00000 $0.00224
Sonnet 5.5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 1mo ago against content hash e23e496ba4b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

performance 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.

.cursor/rules/performance.mdc · 69 lines

What it actually says

Performance & Caching

Data Fetching Rules

  1. Use parallel fetching with Promise.all() when data is independent:
// ✅ CORRECT: Parallel — both requests fire simultaneously
const [user, posts] = await Promise.all([
  getUser(userId),
  getPosts(userId),
])

// ❌ WRONG: Sequential — second request waits for first to finish
const user = await getUser(userId)
const posts = await getPosts(userId)
  1. NEVER fetch in loops (N+1 problem):
// ❌ N+1: Fires 100 queries
for (const id of userIds) {
  const user = await supabase.from('profiles').select().eq('id', id).single()
}

// ✅ Batch: Fires 1 query
const { data } = await supabase.from('profiles').select().in('id', userIds)
  1. Use unstable_cache() for expensive server-side computations:
import { unstable_cache } from 'next/cache'

const getCachedPosts = unstable_cache(
  async (userId: string) => {
    return supabase.from('posts').select().eq('user_id', userId)
  },
  ['user-posts'],
  { revalidate: 60, tags: ['posts'] }
)

Bundle Size Rules

  • Dynamic import heavy libraries: const { Chart } = await import('chart.js')
  • Use next/dynamic for client components that don't need SSR:
import dynamic from 'next/dynamic'
const RichTextEditor = dynamic(() => import('@/components/editor'), {
  ssr: false,
  loading: () => <div className="animate-pulse h-40 bg-muted rounded" />,
})
  • NEVER import entire icon libraries: import { Search } from 'lucide-react' not import * as icons

Image Optimization

  • ALWAYS use next/image with explicit width and height
  • Set priority={true} on above-the-fold hero images for LCP
  • Use placeholder="blur" with blurDataURL for smooth loading
  • Serve modern formats: Next.js automatically converts to WebP/AVIF

Core Web Vitals Targets

  • LCP (Largest Contentful Paint): < 2.5s
  • FID (First Input Delay): < 100ms
  • CLS (Cumulative Layout Shift): < 0.1
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. 1mo ago First seen · 69 lines · 0 tokens per session scan A e23e496ba4b7

Subscribe to this mod's changes

performance is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 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-31.