Your AI coding assistant keeps guessing your conventions. These rules stop that.

What's inside

• 01 Next.js + TypeScript

  Covers App Router structure, Server Components vs. Client Components, data fetching patterns, and Zod validation for API routes. Stops the AI from generating pages/ directory code in an App Router project.

  App Router Server Components Data fetching Zod validation
• 02 Python FastAPI

  Pydantic v2 models, async route patterns, dependency injection with Depends, and consistent error handling shapes. The AI stops generating Pydantic v1 syntax and sync routes in async codebases.

  Pydantic v2 Async patterns Dependency injection Error handling
• 03 Node.js + Express

  Controller/service separation, async error middleware, JWT auth patterns, and standardized response shapes. Prevents the AI from writing inline business logic in route handlers.

  Controller/service pattern Async errors JWT auth Response shapes
• 04 React Native + Expo

  Expo Router file conventions, StyleSheet usage over inline styles, Zustand for local state, TanStack Query for server state, and FlatList performance patterns. Stops the AI from generating bare React Native code that ignores Expo abstractions.

  Expo Router StyleSheet Zustand + TanStack Query FlatList performance
• 05 MCP Server

  Tool vs. resource decisions, the isError pattern for returning errors without crashing the client session, path sandboxing for file access, and Claude Desktop config format. The rule every MCP developer wishes they'd had on day one.

  Tool vs resource decisions isError pattern Path sandboxing Claude Desktop config

How it works

• 1
  Copy the .mdc file into .cursor/rules/ in your project. One file per stack. Pick the one that matches what you're building.
• 2
  Cursor picks it up automatically. No restart needed. The rules are active the next time you open a chat or run Cmd+K.
• 3
  The AI now knows your conventions before writing a line. It uses your patterns, not its defaults.

mkdir -p .cursor/rules
cp nextjs-typescript.mdc .cursor/rules/
# Done. Open Cursor and start a chat.

That's the entire setup. The .cursor/rules/ directory is where Cursor looks for project-level rules. Drop the file in and it's active.

Who it's for

• Cursor users who keep correcting the same AI mistakes on every project
• Developers who've switched to a new stack and want the AI to match it immediately
• Teams that want a shared baseline so Cursor writes consistent code for everyone
• Anyone who's told the AI "we use App Router, not pages" more than twice this week

Questions

• Is this actually useful or just filler content?
  Each rule file targets the specific mistakes Cursor makes for that stack. The Next.js rule stops App Router vs. pages confusion. The FastAPI rule stops Pydantic v1 vs. v2 drift. These aren't generic "write clean code" instructions. They address the exact patterns that break without them.
• Can I get a refund?
  Yes. If you buy it and it's not what you expected, email the address in the download and I'll refund you. No time limit, no questions.
• What format is the download?
  Five .mdc files and a README. Drop the files into .cursor/rules/ and they're active. No build step, no config. The README covers setup and how to customize each rule for your specific project.
• Can I edit the rules to match my specific conventions?
  Yes, that's the point. Open a rule file in Cursor and ask it to adapt the rule to your codebase. The files are plain text. You can add your naming conventions, preferred libraries, or anything else in about 5 minutes.

Pricing

About the author