Browse

Sqlite3 .cursorrules prompt files

SQLite3 is a self-contained, serverless, zero-configuration SQL database engine, ideal for small-scale applications due to its minimal setup and straightforward integration.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

SEO

React.js

Mongoose ODM

JSON Web Tokens

Dusk

Livewire

Alpine.js

PHPUnit

Paraglide.js

WordPress

Sass

MDX

Less

Netlify

Linux

Framer Motion

Formik

next/image

poetry

Ruby

node-gyp

uuid

mime-types

js-yaml

Istio

CSS frameworks

Expo Router

React Query

Server Components

Sentry

Server Actions

RSC

fetch

React Native Testing Library

Detox

HTTPS

expo-localization

ServeMux

Deno

eslint

microservices architecture

AWS API Gateway

OAuth2

Azure Functions

RQ

AWS CloudWatch

AWS Lambda

Kong

Hono

dataclasses

SQLModel

ERC20

Nuqs

camelCase

Riverpod

getIt

filter

Dart

PascalCase

Flutter

CaveatEnforcer

ASCII

SLF4J

ExecutorService

RxJava

Optional

Project Reactor

Pothos

Vue.js 3

Ollama

BEM

LangGraph

Jenkins

Stream API

Java Collections Framework

CSS3

Google Docs

Microsoft Word

CSV

f-strings

Web Vitals

ShadCN UI

React Hook Form

pnpm

Joi

useEffect

Convex

tokio

anyhow

Typer

ES6+

OpenAI API

Passport.js

SVGO

AVIF

Param

Panel

InertiaJS

Catalyst

MLflow

Categories

Clear

Web Development

Frontend Development

Code Style

Programming

Naming Conventions

Testing

State Management

Backend Development

Code Optimization

Software Engineering

Accessibility

Programming Best Practices

Responsive Design

Code Structure

Version Control

Database Management

UI Design

API Development

Code Quality

TypeScript Best Practices

Authentication

TypeScript

Security

Syntax and Formatting

JavaScript

Best Practices

Data Fetching

Internationalization

Coding Best Practices

React

performance optimization

Performance Optimization

Software Development

Coding Standards

API Integration

Object-Oriented Programming

Code Review

Testing and Debugging

Image Optimization

SEO

Game Development

Code Readability

Deployment

Clean Code

User Interface

JavaScript Frameworks

UI Components

UI and Styling

Declarative Programming

Code Modularity

Security Best Practices

Web Application Development

Error Handling

UI Development

JavaScript Libraries

Design Patterns

TypeScript Guidelines

Server-Side Rendering

TypeScript Usage

Programming Guidelines

Modularization

Code Documentation

error handling

functional programming

Coding Style

Scalability

Form Validation

SEO Optimization

Smart Contracts

Dependency Injection

Test-Driven Development

Static Site Generation

Routing

File Organization

Code Organization

Coding Guidelines

Testing and Quality Assurance

Technical Writing

API Design

Node.js

Full Stack Development

Python development

CI/CD

UI/UX design

Functional Programming

Documentation

Python

Validation

Performance

Code Formatting

Python programming

Code Maintainability

Build and Deployment

Decentralized Applications

Artificial Intelligence

Project Management

Web Vitals

Server Components

Blockchain

Coding Practices

Show

5

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Solidity TypeScript .cursorrules prompt file

You are an expert in Solidity, TypeScript, Node.js, postgres, Sqlite3, and Prisma.

Key Principles

Write concise, technical responses with accurate TypeScript examples.
Use functional, declarative programming. Avoid classes.
Prefer iteration and modularization over duplication.
Use descriptive variable names with auxiliary verbs (e.g., isLoading).
Use lowercase with dashes for directories (e.g., components/auth-wizard).
Favor named exports for components.
Use the Receive an Object, Return an Object (RORO) pattern.

JavaScript/TypeScript
Use "function" keyword for pure functions. Omit semicolons.
Use TypeScript for all code. Prefer interfaces over types. Avoid enums, use maps.
File structure: Exported component, subcomponents, helpers, static content, types.
Avoid unnecessary curly braces in conditional statements.
For single-line statements in conditionals, omit curly braces.
Use concise, one-line syntax for simple conditional statements (e.g., if (condition) doSomething()).

Error Handling and Validation
Prioritize error handling and edge cases:
Handle errors and edge cases at the beginning of functions.
Use early returns for error conditions to avoid deeply nested if statements.
Place the happy path last in the function for improved readability.
Avoid unnecessary else statements; use if-return pattern instead.
Use guard clauses to handle preconditions and invalid states early.
Implement proper error logging and user-friendly error messages.
Consider using custom error types or error factories for consistent error handling.