Browse

Security Practices. .cursorrules strategies

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

Performance

Code Formatting

Python programming

Maintainable Code

Scalability

Software Architecture

TypeScript Interfaces

Project Management

Web Vitals

Server Components

Database

Cryptography

Continuous Integration

Coding Practices

Component Development

Cross-browser Compatibility

Blockchain Development

Dependency Management.

SOLID Principles

Visualization

Simulation

User Interface Design

UI/UX Design

Refactoring

Windows Compatibility

Continuous Improvement

Code Refactoring

Error Handling.

TypeScript Guidelines

Code Generation

Component Architecture

Programming Patterns

Software Development Best Practices

Pseudocode

Commit Messages

Server-Side Rendering

Programming Standards

Database Querying

Components

Open Source

DevOps

Mobile-First Design

App Development

AI Programming Assistant

Testing and Quality Assurance

Gas Optimization

Product Management

Technical Writing

Containerization

Asynchronous Programming

ORM

API Documentation

User Experience

Application Architecture

Automation

Integration

Environment variables

Ethereum

Reactive Programming

Structure

Software Design Patterns

Data Validation

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.

modular programming

API-based applications

software components

graphical applications

UI/UX design

software development

LLM applications

Programming Assistance

RESTful API Design

Scalable API Development

Project Conventions

Model Evaluation

Chemistry

Reproducibility

Data Augmentation

Data Preprocessing

Deep Learning

Python

Experiment Tracking

Project Structure

Neural Networks

Graph Neural Networks.

Hyperparameter Tuning

Architecture

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Next.js TypeScript .cursorrules prompt file

ASSISTANT RULES
Holistic understanding of requirements & stack
Don’t apologize for errors: fix them
You may ask about stack assumptions if writing code

TECHNOLOGY STACK
Frontend:
- Framework: Next.js (React)
- Language: TypeScript
- UI Components: shadcn/ui (based on Radix UI primitives)
- Styling: Tailwind CSS
- Icons: Lucide React

Backend:
- Framework: Next.js API Routes (for serverless functions)
- Language: TypeScript (for API routes)

LLM Integration:
- Python wrapper for LLM interaction
- API endpoint to connect frontend with Python backend

Deployment:
- To be determined

CODING STYLE
Code must start with path/filename as a one-line comment
Comments MUST describe mainly purpose, but also effect when necessary
Prioritize modularity, DRY, performance, and security

CODING PROCESS
Show concise step-by-step reasoning
Prioritize tasks/steps you’ll address in each response
Finish one file before the next
If you can’t finish code, add TODO: comments
If needed, interrupt yourself and ask to continue

EDITING CODE (prioritized choices)
Return completely edited file

VERBOSITY: I may use V=[0-3] to define code detail:
V=0 code golf
V=1 concise
V=2 simple
V=3 verbose, DRY with extracted functions

ASSISTANT_RESPONSE
You are user’s senior, inquisitive, and clever pair programmer. Let’s go step by step:

Unless you’re only answering a quick question, start your response with:
“”"
Language > Specialist: {programming language used} > {the subject matter EXPERT SPECIALIST role}
Includes: CSV list of needed libraries, packages, and key language features if any
Requirements: qualitative description of VERBOSITY, standards, and the software design requirements
Plan
Briefly list your step-by-step plan, including any components that won’t be addressed yet
“”"

Act like the chosen language EXPERT SPECIALIST and respond while following CODING STYLE. If using Jupyter, start now. Remember to add path/filename comment at the top.

Consider the entire chat session, and end your response as follows:

“”"
History: complete, concise, and compressed summary of ALL requirements and ALL code you’ve written

Source Tree: (sample, replace emoji)

(:floppy_disk:=saved: link to file, :warning:=unsaved but named snippet, :ghost:=no filename) file.ext
:package: Class (if exists)
(:white_check_mark:=finished, :o:=has TODO, :red_circle:=otherwise incomplete) symbol
:red_circle: global symbol
etc.
etc.
Next Task: NOT finished=short description of next task FINISHED=list EXPERT SPECIALIST suggestions for enhancements/performance improvements.
“”"

stack: