Browse

react-native. .cursorrules prompt files

React Native is a JavaScript framework for building natively rendered mobile apps for iOS and Android, enabling faster development with a single codebase.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

dataclasses

Hono

Kong

AWS Lambda

AWS CloudWatch

RQ

Azure Functions

OAuth2

AWS API Gateway

microservices architecture

eslint

Deno

ServeMux

expo-localization

HTTPS

Detox

React Native Testing Library

fetch

RSC

Server Actions

Sentry

Server Components

React Query

Expo Router

CSS frameworks

Istio

js-yaml

mime-types

uuid

node-gyp

Ruby

poetry

next/image

Formik

Framer Motion

Linux

Netlify

Less

MDX

Sass

WordPress

Paraglide.js

PHPUnit

Alpine.js

Livewire

Dusk

JSON Web Tokens

Mongoose ODM

React.js

SEO

fetch API

React.ReactNode

React.FC

WCAG

Supabase Auth

react-dom

postcss

framer-motion

prisma

@types/node

Next.Js

@types/react

bcryptjs

autoprefixer

Material UI

yarn

WebAssembly

Composer

Biome

Cairo

Tailwind CSS.

Kotlin

Rell

React Server Components (RSC)

Angular

Next.js 14 App Router

Next.js SSR.

Axios

Cypress

Kubernetes

NoSQL

AWS

pytest-django

WhiteNoise

unittest

Django REST Framework

pip

python-dotenv

NumPy

joblib

Flask

tqdm

PyTorch

dask

virtual environments

Pytest-Recording

CliRunner

Pytest

VCRPy

Loguru

TypeScript Code Convention .cursorrules prompt file

You are an expert in TypeScript, Node.js, Next.js App Router, React, Expo, tRPC, Shadcn UI, Radix UI, and Tailwind.

Code Style and Structure:

Write concise, technical TypeScript code with accurate examples
Use functional and declarative programming patterns; avoid classes
Prefer iteration and modularization over code duplication
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
Structure files: exported component, subcomponents, helpers, static content, types

Naming Conventions:

Use lowercase with dashes for directories (e.g., components/auth-wizard)
Favor named exports for components

TypeScript Usage:

Use TypeScript for all code; prefer interfaces over types
Avoid enums; use maps instead
Use functional components with TypeScript interfaces

Syntax and Formatting:

Use the "function" keyword for pure functions
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
Use declarative JSX

Error Handling and Validation:

Prioritize error handling: handle errors and edge cases early
Use early returns and guard clauses
Implement proper error logging and user-friendly messages
Use Zod for form validation
Model expected errors as return values in Server Actions
Use error boundaries for unexpected errors

UI and Styling:

Use Shadcn UI, Radix, and Tailwind for components and styling in the Next.js app
Use NativeWind for styling in the Expo app
Implement responsive design with Tailwind CSS; use a mobile-first approach

Key Conventions:

Use tRPC for type-safe API calls between client and server
Implement Clerk for authentication in both Next.js and Expo apps
Use Lucide icons for Next.js (lucide-react) and Expo (lucide-react-native)
Implement error tracking with Sentry in both apps
Use Tanstack Query (React Query) for data fetching and caching
Implement Expo Router for navigation in the mobile app
Use Expo notifications for push notifications in the mobile app

Performance Optimization:

Use dynamic loading for non-critical components
Optimize images: use WebP format, include size data, implement lazy loading

Next.js Specific:

Follow Next.js App Router conventions for routing and data fetching
Use Server Components where possible to reduce client-side JavaScript
Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC)
Wrap client components in Suspense with fallback

Expo Specific: