Browse

Redux .cursorrules prompt files

Redux is a state management library for JavaScript applications, providing a predictable and centralized state container to facilitate debugging and ease state management across components.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

Supabase

CSS

HTML

Next.js App Router

Jest

Docker

PostgreSQL

Redis

TailwindCSS

Tailwind Aria

Pydantic

ESLint

Git

FastAPI

JSDoc

Vercel

Solidity

react-hook-form

pytest

React Testing Library

Zustand

ARIA

Vitest

Suspense

Prettier

Typescript

GitHub Actions

Shadcn

Radix

Celery

dotenv

Prisma

SSR

PEP 8

Expo

Clerk

tRPC

MongoDB

Pinia

Vue.js

JSON

SvelteKit

PHP

SQLAlchemy

Express

VueUse

Drizzle ORM

RESTful API

Laravel

DaisyUI

tanStackQuery

Playwright

SQL

SQLite

GitLab CI

Swagger

JWT

Lighthouse

CORS

Flexbox

Stripe

Drizzle

OpenZeppelin

Markdown

Svelte 5

Astro

Vue Router

styled-components

Nuxt 3

ES6

Elixir

Svelte

GraphQL

Java

Rust

RabbitMQ

GitHub

pandas

scikit-learn

TypeScript

asyncpg

Mongoose

TanStack React Query

None

Turborepo

React Server Components

Clear

Web Development

Frontend Development

Programming

Code Style

Naming Conventions

Testing

State Management

Backend Development

Software Engineering

Code Optimization

Responsive Design

Programming Best Practices

Accessibility

UI Design

Database Management

Version Control

Code Structure

API Development

TypeScript

Authentication

TypeScript Best Practices

Code Quality

Syntax and Formatting

Security

JavaScript

Data Fetching

Best Practices

React

Coding Best Practices

Internationalization

Object-Oriented Programming

API Integration

Coding Standards

Software Development

Performance Optimization

performance optimization

Game Development

SEO

Image Optimization

Testing and Debugging

Code Review

UI and Styling

UI Components

JavaScript Frameworks

User Interface

Clean Code

Deployment

Code Readability

Code Documentation

Modularization

Programming Guidelines

TypeScript Usage

Server-Side Rendering

TypeScript Guidelines

Design Patterns

JavaScript Libraries

UI Development

Error Handling

Web Application Development

Security Best Practices

Code Modularity

Declarative Programming

Full Stack Development

Node.js

API Design

Technical Writing

Testing and Quality Assurance

Coding Guidelines

Code Organization

File Organization

Routing

Static Site Generation

Test-Driven Development

Dependency Injection

Smart Contracts

SEO Optimization

Form Validation

Scalability

Coding Style

functional programming

error handling

Python Libraries

Structure

Semantic HTML

Game Design

Ethereum

React Best Practices

Automation

Vue.js

Next.js

Microservices

Serverless Architecture

Cloud Computing

Form Handling

App Development

Mobile-First Design

DevOps

Styling

Content Management

Clean Code Practices

Show

5

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

TypeScript Python FastAPI React Best Practices .cursorrules prompt file

Frontend (TypeScript/React):

Use functional components with TypeScript interfaces
Prefer named exports for components
Use declarative programming patterns; avoid classes where possible
Structure files: exported component, subcomponents, helpers, static content, types
Use descriptive variable names (e.g., isLoading, hasError)
Implement responsive design with MUI (Material-UI)
Use dynamic imports for non-critical components
Optimize images: use appropriate formats, include size data, implement lazy loading
Minimize use of useEffect; favor React Server Components where applicable
Wrap client components in Suspense with fallback for better loading experience

TypeScript Usage:

Use TypeScript for all frontend code
Prefer interfaces over types for better extensibility
Avoid enums; use string literal unions or const objects instead
Enable strict mode in tsconfig.json

Naming Conventions:

Use PascalCase for component files (e.g., SubscriptionList.tsx)
Use camelCase for non-component files (e.g., urlUtils.ts)
Use lowercase with dashes for directories (e.g., components/add-subscription)

Syntax and Formatting:

Use arrow functions for component definitions and callbacks
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
Use optional chaining (?.) and nullish coalescing (??) operators
Prefer template literals over string concatenation

Error Handling and Validation:

Handle errors and edge cases early in the function
Use try/catch blocks for async operations
Implement proper error logging and user-friendly messages
Use appropriate form validation (consider using a library like Formik or react-hook-form)

State Management:

Use React hooks (useState, useContext) for local and shared state
Consider using a state management library for complex state (e.g., Redux, Recoil)

Backend (Python):

Use Python 3.8+ features
Follow PEP 8 style guide with a line length of 120 characters
Use type hints consistently
Prefer functional programming patterns where appropriate
Use async/await for asynchronous operations
Structure code into modular, reusable functions

Python Specifics:

Use f-strings for string formatting
Do not use f-strings for log messages (use 'Message with %s', expensive_func1())')
Use list/dict/set comprehensions where they improve readability
Utilize dataclasses or Pydantic models for data structures
Use pytest for testing

Naming Conventions:

Use snake_case for function and variable names
Use PascalCase for class names
Use UPPER_CASE for constants

Error Handling:

Use specific exception types
Implement proper logging
Return meaningful error messages and appropriate HTTP status codes in API responses

API Design:

Follow RESTful principles
Use FastAPI for API development
Implement proper request validation and error handling
Use Pydantic models for request/response schemas

Database:

Use SQLModel for ORM (https://sqlmodel.tiangolo.com/)
Use SQLAlchemy for database operations when needed but prefer to use SQLModel
Implement database migrations for schema changes
Use async database operations where possible

General:

Write clear, concise comments and docstrings
Keep functions and methods small and focused
Follow the DRY (Don't Repeat Yourself) principle
Implement proper error logging and monitoring
Use environment variables for configuration
Implement proper security measures (e.g., input validation, CORS, authentication)

Version Control: