Browse

NativeWind .cursorrules prompt files

NativeWind is a software development framework that enables developers to build native mobile and web applications with faster performance, improved user experiences, and reduced development time.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

Discord.py

obsidian

RBAC

Google Calendar

ShadCN-UI

ShadCN-Graphs

nextjs app router

EditorConfig

Google Chat

Obsidian Plugin Development

Tanstack Start

React Router

React Query SSR

Vinxi

Go templating

Hugo

SCSS

SASS

Marisco

fastcore

nbdev

NetCDF

Vercel KV

Genql

Polaris

Shopify Admin GraphQL API

module css

frame motion

temporal

memo

useImmerReducer

useMemo

useCallback

cn utility

YAML

SIFT

OpenCV

ORB

SoundDevice

RPi.GPIO

scikit-image

Supabase/Postgres

Supabase Client API

lucide

magicui

shadcn

tailwind

TS

loggo

testify

taskfile.dev

Jupyter Notebook

RGAA

Mux

Prisma ORM

Shadcn UI components

RevenueCat

Lucide icons

React.memo()

TypeORM

Apollo Graphql

Postcss

swr

Lerna

API development

npm workspaces

Nx

serverless environments

NotifierProvider

JsonSerializable

ListView.builder

GoRouter

build_runner

AsyncNotifierProvider

Freezed

StateProvider

auto_route

AssetImage

StateNotifierProvider

Riverpod Hooks

JsonValue

cached_network_image

Flutter Hooks

ChangeNotifierProvider

JsonKey

react-hook-form.

Jetstream

Pest

Inertia.js

Prime React

Postgres

ExpressJs

prom-client

sequelize

winston

morgan

redis

GitHub Pages

AlpineJS

HTMX

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: