PromptKit – 50 production-ready .cursorrules and CLAUDE.md files for Cursor users

Showcase Built for Cursor
1

Hey Cursor community!

I got frustrated writing .cursorrules files from scratch for every new project, so I built PromptKit — 50 production-ready prompts and rules built specifically for Cursor and Claude Code users.

What’s included

10 x .cursorrules files — drop-in ready for:

  • React + TypeScript
  • Next.js App Router
  • Python FastAPI
  • Go REST API
  • Node.js Express
  • Flutter
  • Django
  • SvelteKit
  • Rust CLI
  • Universal (works with any stack)

5 x CLAUDE.md setup files for Claude Code — pre-built project context for React, Node.js API, Python data projects, Full-stack SaaS, and Open source libraries.

35 more prompts covering code review (security audit, refactoring, rubber duck debugging, test writing), startup writing (cold emails, landing copy, pitch decks), and product thinking (PRDs, prioritization, post-mortems).

Why it’s useful

Every time I started a new project I’d spend 20 min writing a .cursorrules file from scratch. Now I drop one in and Cursor immediately understands my conventions, preferred patterns, and what to avoid.

The CLAUDE.md files are the same idea for Claude Code — it asks far fewer clarifying questions with proper project context upfront.

Link

https://moderna8.gumroad.com/l/fjtei — $19, instant download.

Happy to paste any of the individual rules in the comments if you want to see what’s inside first. Would love feedback on what stacks are missing!

3

Here’s a free sample — the React + TypeScript .cursorrules file:

## Code style
- Functional components only, no class components
- TypeScript strict mode always
- Named exports only, no default exports (except pages)
- Props interface defined above the component, named [ComponentName]Props

## File structure
- components/[Name]/index.tsx + [Name].module.css
- hooks/ for all custom hooks, prefixed with "use"
- utils/ for pure functions only
- types/ for shared TypeScript interfaces

## Patterns to always use
- React.memo() for expensive list items
- useCallback for handlers passed as props
- Zod for all runtime validation
- React Query for server state, Zustand for client state

## Patterns to never use
- any type (use unknown instead)
- // @ts-ignore (fix the type instead)
- Inline styles (use CSS modules)
- useEffect for data fetching (use React Query)

The pack has 9 more of these plus 5 CLAUDE.md files and 35 prompts total. Let me know if you want to see any others!

4

Here’s the Next.js App Router .cursorrules file as another free sample:

## Architecture
- App Router only, no Pages Router patterns
- Server Components by default, Client Components only when needed
- Server Actions for mutations (no API routes for internal data)
- Route handlers only for external webhooks

## File conventions
- page.tsx for routes
- layout.tsx for shared layouts
- loading.tsx for Suspense boundaries
- error.tsx for error boundaries
- actions.ts for Server Actions

## Data fetching
- fetch() with proper cache/revalidate in Server Components
- React Query for client-side real-time data
- Never fetch in useEffect

## Performance rules
- Images always via next/image with proper sizes
- Fonts via next/font only
- Dynamic imports for heavy client components
- Metadata export on every page.tsx

## TypeScript
- Strict mode on
- No 'any', ever
- Generate types from Prisma schema for DB models

Which stack would you like to see next? Go, FastAPI, Node.js, or something else?