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

React

Tailwind CSS

Node.js

Tailwind

Shadcn UI

JavaScript

Python

Radix UI

Next.js

Vite

JSX

WebP

Zod

Docker

Next.js App Router

Supabase

CSS

PostgreSQL

Redis

FastAPI

HTML

Pydantic

pytest

Git

Jest

react-hook-form

Solidity

Vercel

SQLAlchemy

Tailwind Aria

Suspense

SvelteKit

Vue.js

GitHub Actions

Celery

ESLint

PHP

TailwindCSS

Pinia

PEP 8

asyncpg

TypeScript

SQL

Playwright

Svelte

Prettier

Radix

DaisyUI

Vitest

JSDoc

JSON

ARIA

Drizzle ORM

Vue Router

VueUse

Astro

Svelte 5

tRPC

Expo

CORS

aiomysql

GitLab CI

Django

Typescript

scikit-learn

pandas

GitHub

RabbitMQ

Java

WebP.

tanStackQuery

Phoenix LiveView

Ecto

File System Watcher

Plug

Finch

Gettext

Phoenix

Elixir

Jason

Phoenix LiveDashboard

Sobelow

ExCoveralls

DNS Cluster

ExUnit

Release Please

Swoosh

Credo

LeftHook

ES6

npm

Laravel

styled-components

RESTful API

Shadcn

Markdown

OpenZeppelin

Slither

Hardhat

Mythril

Clear

Behavior

Configuration Management

Monitoring

Logging

Libraries

Dependency Management

Project Specific

code best practices

data validation

Jupyter Notebook

data analysis

data visualization

PEP 8 guidelines

EEG application development

Software development best practices.

User interface design

Signal processing

LLM Integration

Security Practices.

Project Structuring.

Open Source Tools

Coding Principles

Caching

CI/CD Pipelines

Data Infrastructure

Server-Side Programming

Cloud Platforms

Logging and Monitoring

Microservices Architecture

Containerization and Orchestration

Data Modeling

Desktop Application Development

Programming Best Practices.

API Communication

File Structure.

Web Development.

Blockchain Technology

User Interface Development

Software Development Best Practices

Code Performance

Software Refactoring

Debugging

Problem Solving.

Front-end Development

Technology Integration

Dynamic Loading.

URL State Management

Code Examples

Commit Guidelines

Reusable Code

Frontend Development.

Modular Design

Gas Efficiency

Commit Messaging

Automated Testing

Dynamic Routing

Reusability

Continuous Integration.

Animation and Transition

Programming Instructions

UI/UX

Component Design

PHP 7.4 Features

PSR-12 Coding Standards

Web Application

Backend Integration

Cellular Automata

Environmental Simulation

Data Synchronization

Shader Programming

User Interaction

Interactive Systems

Grid Systems

Generative User Interfaces

Middleware Integration

AI SDK Integration

Deployment Considerations

React Server Components

Business Process Modeling

BPMN Diagrams

Project Management Tools

Business Analysis

AI Chatbot

Code Implementation Guidelines

Component-Based Development

Accessibility in Web Design

Modern Web Technologies

Documentation structure

Development guidelines

Coding standards

Testing strategy

Package integration

Code structure

Laravel package development

Browser APIs.

Code Architecture

Web Security

Functional Programming.

Error Boundaries

TypeScript Conventions.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

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: