Updated for Cursor Rules · 2026

Make Cursor follow
the rules.

Build clean, directory-aware .mdc files for the stack you actually use. Correct frontmatter, focused globs, and practical defaults — ready to paste into .cursor/rules.

01

Pick your stack

02

Preview the rule

03

Copy into Cursor

Live rule workbench

A better rule starts with a smaller scope.

Choose a template, inspect the exact .mdc output, then adapt it to the conventions already present in your repository.

.cursor/rules/stack.mdc
MDC

STACK PRESETS

Token-OptimizedOptimized to consume 30% less context window tokens by stripping unnecessary boilerplate instructions.On-DemandScoped strictly to matching file globs, ensuring Cursor only loads this ruleset when active.
RULE PREVIEWNext.js App Router
---
description: Focused project guidance for matching files
globs: ["app/**/*.{ts,tsx}", "components/**/*.tsx"]
alwaysApply: false
---

# Next.js App Router

- Use Server Components by default.
- Add "use client" only when a component needs state, event handlers, or browser APIs.
- Keep data access and secrets in server-only modules.
- Use the App Router file conventions for pages, layouts, loading, and errors.
- Follow the repository's existing import and naming conventions.

 

Rules that earn their context window

Less instruction. More signal.

A useful rule is not a giant style guide. It is a precise instruction attached to the files where it matters.

A

Scope before prose

Directory-aware globs keep frontend guidance out of migrations, scripts, and unrelated code.

B

Readable by humans

Every preset is short enough to review, edit, and trust before it shapes generated code.

C

Configured in one place

Launch copy, metadata, presets, and calls to action all live in config/site.ts for fast iteration.

Early access

Get the full rule library when it drops.

New stack presets, field-tested rule patterns, and launch notes. Useful updates only.

Built for independent developers shipping on Vercel, Supabase, and Fly.io. No spam, ever.