Browse

Expo SDK .cursorrules prompt files

Expo SDK is a toolset for building cross-platform React Native applications, offering convenient APIs and components to streamline app development and improve efficiency.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

OpenAPI

Grid

API

async/await

Grafana

ELK Stack

Memcached

Prometheus

SWR

SVG

OpenAI

SOLID

Chainlink VRF

Mythril

Hardhat

Slither

Firebase

Vercel AI SDK

Express.js

Daisy UI

Next.js 14

Viem

Wagmi

npm

LeftHook

Credo

Swoosh

Release Please

ExUnit

DNS Cluster

ExCoveralls

Sobelow

Phoenix LiveDashboard

Jason

Phoenix

Gettext

Finch

Plug

File System Watcher

Ecto

Phoenix LiveView

next-safe-action

WebP.

Kafka

Go

MySQL

Azure

logging

Tauri

seaborn

matplotlib

Django

Langchain

Ruff

aiomysql

AVIF

SVGO

Passport.js

OpenAI API

ES6+

Typer

anyhow

tokio

Convex

useEffect

Joi

pnpm

React Hook Form

ShadCN UI

Web Vitals

f-strings

CSV

Microsoft Word

Google Docs

CSS3

Java Collections Framework

Stream API

Jenkins

LangGraph

BEM

Ollama

Vue.js 3

Pothos

Project Reactor

Optional

RxJava

ExecutorService

SLF4J

ASCII

CaveatEnforcer

Flutter

PascalCase

Dart

filter

getIt

Riverpod

camelCase

Nuqs

ERC20

SQLModel

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: