Browse

KV .cursorrules prompt files

KV, or Kubernetes Volume, is a storage abstraction that enhances container application portability and persistence by allowing data to be shared across multiple pods and nodes.

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

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Security Considerations

Software Design Patterns

Data Validation

Tailwind CSS

Component Modularity

Mobile App Development

Data Storage

Git Workflow

System Design

Styling and Design

Data Transformation

animations

Simulations

Multi-Agent Systems

middleware

response schemas

scalable API development

caching strategies

input validation

AI-friendly coding practices

configuration management

project structure

type hints

debugging

code style consistency

logging

modular design

code snippets.

API-based applications

software components

graphical applications

software development

LLM applications

Programming Assistance

Scalable API Development

Project Conventions

Model Evaluation

Chemistry

Reproducibility

Data Augmentation

Data Preprocessing

Deep Learning

Experiment Tracking

Project Structure

Neural Networks

Graph Neural Networks.

Hyperparameter Tuning

Architecture

Behavior

Configuration Management

Monitoring

Logging

Libraries

Dependency Management

Project Specific

code best practices

data validation

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

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.

Technology Integration

Dynamic Loading.

URL State Management

Code Examples

Commit Guidelines

Reusable Code

Frontend Development.

Modular Design

Gas Efficiency

Commit Messaging

Automated Testing

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

TypeScript React Next.js Cloudflare .cursorrules prompt file

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

You are also excellent at Cloudflare developer tools like D1 serverless database and KV. You can suggest usage of new tools (changes in wrangler.toml file) to add more primitives like:

R2: File storage
KV: Key-value storage
AI: AI multimodal inference
others primitives in wrangler.toml
In the terminal, you are also an expert at suggesting wrangler commands.
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.
UI and Styling
Use Shadcn UI, Radix, and Tailwind for components and styling.
Implement responsive design with Tailwind CSS; use a mobile-first approach.
Performance Optimization
Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).
Wrap client components in Suspense with fallback.
Use dynamic loading for non-critical components.
Optimize images: use WebP format, include size data, implement lazy loading.
Key Conventions
Use 'nuqs' for URL search parameter state management.
Optimize Web Vitals (LCP, CLS, FID).
Limit 'use client':
- Favor server components and Next.js SSR.
- Use only for Web API access in small components.
- Avoid for data fetching or state management.
Follow Next.js docs for Data Fetching, Rendering, and Routing.