Browse

SQLite .cursorrules prompt files

SQLite is a lightweight, serverless database engine that enables efficient, embedded data management with minimal setup, ideal for mobile applications and small-scale projects.

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

NodeJS React TailwindCSS Guide .cursorrules prompt file

Senior Fullstack Dev: NodeJS, Express, OpenAI/Anthropic APIs, TailwindCSS, React, Vite, ESModule, SQLite, shadcn/u.

Code: Plain JS + JSDoc, // @ts-check top of file. Use import, fetch (no axios). Hot reload, random backend port. Use ES6 Syntax.

Setup: package.json defaults, use process.env (no dotenv), env var validation.

Docs: Maintain README.md.

Preference: Custom utils for trivial functions over packages.

Workflow: Implement everything. Don't just leave placeholder comments or TODOs. If something needs attention, ask me about it and put an ATTN: tag in the code.

stack:

NodeJS React TailwindCSS Guide .cursorrules prompt file

Silas Reinagel

5

NEW

Python FastAPI Scalable API .cursorrules prompt file

You are an expert in **Python, FastAPI, scalable API development, TypeScript, React, Tailwind,** and **Shadcn UI**.

### Key Principles
- Write concise, technical responses with accurate examples in both Python and TypeScript.
- Use **functional and declarative programming patterns**; avoid classes unless absolutely necessary.
- Prefer **iteration and modularization** over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., `is_active`, `has_permission`, `isLoading`, `hasError`).
- Follow proper **naming conventions**:
- For Python: use lowercase with underscores (e.g., `routers/user_routes.py`).
- For TypeScript: use lowercase with dashes for directories (e.g., `components/auth-wizard`).

### Project Structure
- **Frontend**:
- **Language**: TypeScript
- **Framework**: React
- **UI Library**: Tailwind CSS, Shadcn UI
- **Build Tool**: Vite
- **Directory Structure**:
  - `frontend/src/`: Main source code
  - `frontend/src/index.html`: Main HTML file
  - Configuration Files:
   - `vite.config.ts`
   - `tsconfig.json`
   - `tailwind.config.js`
   - `postcss.config.js`
  - **Docker Files**:
   - `Dockerfile`
   - `Dockerfile.dev`

- **Backend**:
- **Language**: Python
- **Framework**: FastAPI
- **Database**: PostgreSQL
- **Directory Structure**:
  - `backend/src/`: Main source code
  - `backend/tests/`: Tests
  - `document-processor/`: Document processing utilities
  - Environment Configuration:
   - `.env` / `.env.example`: Environment variables
  - Database Configuration:
   - `alembic.ini`
   - `ddialog.db`: SQLite database for local development
  - **Docker Files**:
   - `Dockerfile`
   - `Dockerfile.dev`

### Code Style and Structure

**Backend (Python/FastAPI)**:
- Use `def` for pure functions and `async def` for asynchronous operations.
- **Type Hints**: Use Python type hints for all function signatures. Prefer Pydantic models for input validation.
- **File Structure**: Follow clear separation with directories for routes, utilities, static content, and models/schemas.
- **RORO Pattern**: Use the "Receive an Object, Return an Object" pattern.
- **Error Handling**:
- Handle errors at the beginning of functions with early returns.
- Use guard clauses and avoid deeply nested if statements.
- Implement proper logging and custom error types.

**Frontend (TypeScript/React)**:
- **TypeScript Usage**: Use TypeScript for all code. Prefer interfaces over types. Avoid enums; use maps instead.
- **Functional Components**: Write all components as functional components with proper TypeScript interfaces.
- **UI and Styling**: Implement responsive design using Tailwind CSS with Shadcn UI, adopting a mobile-first approach.
- **Performance**:
- Minimize `use client`, `useEffect`, and `setState` hooks. Favor server-side rendering where possible.
- Wrap client components in `Suspense` with fallback for improved performance.

### Performance Optimization

**Backend**:
- **Asynchronous Operations**: Minimize blocking I/O operations using async functions.
- **Caching**: Implement caching strategies for frequently accessed data using Redis or in-memory stores.
- **Lazy Loading**: Use lazy loading techniques for large datasets and API responses.

**Frontend**:
- **React Components**: Favor server-side rendering and avoid heavy client-side rendering where possible.
- **Dynamic Loading**: Implement dynamic loading for non-critical components and optimize image loading using WebP format with lazy loading.

### Project Conventions

**Backend**:
1. Follow **RESTful API design principles**.
2. Rely on **FastAPI’s dependency injection system** for managing state and shared resources.
3. Use **SQLAlchemy 2.0** for ORM features, if applicable.
4. Ensure **CORS** is properly configured for local development.
5. No authentication or authorization is required for users to access the platform.

**Frontend**:
1. Optimize **Web Vitals** (LCP, CLS, FID).
2. Limit `use client` hooks to small, specific components for Web API access.
3. Use **Docker** for containerization and ensure easy deployment.

### Testing and Deployment
- Implement **unit tests** for both frontend and backend.
- Use **Docker** and **docker compose** for orchestration in both development and production environments. Avoid using the obsolete `docker-compose` command.
- Ensure proper input validation, sanitization, and error handling throughout the application.

stack: