Teach your editor how your stack writes code

Rules

Showing 9 loaded rules

• Expo + React Native

  19 lines

  Cross-platform mobile development with Expo Router, typed navigation, and performant lists.

  • React Native
  • Expo
  • Mobile

  .cursorrulesCopyExpo + React Native rules

  1You are an expert in TypeScript, React Native, Expo, and mobile UI development.2 3Project4- Use Expo Router for file-based navigation.5- Use Expo SDK modules before reaching for bare native libraries.6- Keep platform-specific code in .ios.tsx / .android.tsx files.7 8UI9- Use SafeAreaView and useSafeAreaInsets for notches and home bars.

  + 10 more lines — copy to get the full ruleset

• Go Backend Services

  20 lines

  Idiomatic Go for production HTTP services: small interfaces, explicit errors, and context everywhere.

  • Go
  • API
  • Backend

  .cursorrulesCopyGo Backend Services rules

  1You are an expert Go engineer building production backend services.2 3Structure4- Organize by domain, not by layer (internal/billing, internal/users).5- Keep main.go thin: parse config, wire dependencies, start server.6- Define interfaces where they are consumed, and keep them small.7 8Errors9- Return errors; never panic in request paths.

  + 11 more lines — copy to get the full ruleset

• Laravel

  20 lines

  Modern Laravel conventions with Eloquent, form requests, queues, and Pest testing.

  • PHP
  • Laravel
  • Backend

  .cursorrulesCopyLaravel rules

  1You are an expert in Laravel, PHP 8.3, and modern web application architecture.2 3Conventions4- Follow PSR-12 and Laravel naming conventions.5- Use strict types: declare(strict_types=1) in every file.6- Prefer constructor property promotion and readonly properties.7 8HTTP9- Validate input with Form Request classes, never in controllers.

  + 11 more lines — copy to get the full ruleset

• Next.js App Router

  21 lines

  Server-first conventions for Next.js App Router projects with React Server Components, Server Actions, and strict TypeScript.

  • Next.js
  • React
  • TypeScript

  .cursorrulesCopyNext.js App Router rules

  1You are an expert in TypeScript, Next.js App Router, React, and Tailwind CSS.2 3Code Style4- Write concise, technical TypeScript with accurate types.5- Prefer functional, declarative patterns; avoid classes.6- Use descriptive names with auxiliary verbs (isLoading, hasError).7 8React Server Components9- Default to Server Components; add 'use client' only for interactivity.

  + 12 more lines — copy to get the full ruleset

• Python FastAPI

  21 lines

  Guidelines for scalable FastAPI services using Pydantic v2, async I/O, and dependency injection.

  • Python
  • FastAPI
  • API

  .cursorrulesCopyPython FastAPI rules

  1You are an expert in Python, FastAPI, and scalable API development.2 3Key Principles4- Write concise, technical responses with accurate Python examples.5- Use functional, declarative programming; avoid classes where possible.6- Use lowercase with underscores for files and directories (routers/user_routes.py).7 8FastAPI9- Use `def` for pure functions and `async def` for I/O-bound operations.

  + 12 more lines — copy to get the full ruleset

• Rust

  20 lines

  Safe, ergonomic Rust with clear ownership, typed errors, and async Tokio services.

  • Rust
  • Systems

  .cursorrulesCopyRust rules

  1You are an expert in Rust, async programming with Tokio, and systems design.2 3Ownership4- Prefer borrowing over cloning; clone deliberately and visibly.5- Use &str and &[T] in function parameters for flexibility.6- Reach for Arc<Mutex<T>> only when shared mutation is unavoidable.7 8Errors9- Use thiserror for library error types and anyhow in binaries.

  + 11 more lines — copy to get the full ruleset

• SvelteKit

  19 lines

  Svelte 5 runes, load functions, and form actions for fast, progressively enhanced SvelteKit apps.

  • Svelte
  • SvelteKit
  • TypeScript

  .cursorrulesCopySvelteKit rules

  1You are an expert in Svelte 5, SvelteKit, and TypeScript.2 3Reactivity4- Use runes: $state for local state, $derived for computed values.5- Use $effect sparingly, only for syncing with external systems.6- Declare component inputs with $props() and type them.7 8Routing & Data9- Load data in +page.server.ts for secrets and database access.

  + 10 more lines — copy to get the full ruleset

• Tailwind CSS v4

  20 lines

  Design-token driven styling with Tailwind v4, CSS-first configuration, and accessible component patterns.

  • Tailwind
  • CSS
  • Design

  .cursorrulesCopyTailwind CSS v4 rules

  1You are an expert in Tailwind CSS v4 and modern CSS architecture.2 3Configuration4- Configure the theme in CSS using @theme; there is no tailwind.config.js.5- Define colors as semantic tokens (--color-background, --color-primary).6- Never hardcode hex values in class names; use theme tokens.7 8Layout9- Use flexbox first, grid for true two-dimensional layouts.

  + 11 more lines — copy to get the full ruleset

• TypeScript Strict

  19 lines

  A no-compromise ruleset for type-safe TypeScript codebases: explicit boundaries, narrow types, and zero any.

  • TypeScript

  .cursorrulesCopyTypeScript Strict rules

  1You are a senior TypeScript engineer who values correctness over cleverness.2 3Types4- Never use `any`. Prefer `unknown` and narrow with type guards.5- Prefer `type` aliases for unions and `interface` for object contracts.6- Use discriminated unions to model state instead of optional flags.7- Mark data as `readonly` unless mutation is required.8 9Functions

  + 10 more lines — copy to get the full ruleset