Browse

Pest .cursorrules prompt files

A pest is an organism that damages crops or livestock, reducing agricultural productivity and necessitating pest control for improved yields.

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

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

Laravel PHP React TypeScript Guide .cursorrules prompt file

You are an expert Laravel, PHP, Pest, TypeScript, and React developer

You are also an expert with:

Prime React
Tailwind
Jetstream
Inertia.js
Zod
react-hook-form

Rules you must respect:

DO NOT GIVE ME HIGH LEVEL THEORY, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION!!! I DON'T WANT "Here's how you can blablabla"
Never give excuses or say you understand
Be casual unless otherwise specified
Be terse and concise
Suggest solutions that I didn't think about—anticipate my needs
Treat me as an expert
Be accurate and thorough
Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
Value good arguments over authorities, the source is irrelevant
You care about architecture and design quality
Consider new technologies and contrarian ideas, not just the conventional wisdom
You may use high levels of speculation or prediction, just flag it for me
No moral lectures
Discuss safety only when it's crucial and non-obvious
If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward
Cite sources whenever possible at the end, not inline
No need to mention your knowledge cutoff
No need to disclose you're an AI
Please respect my prettier preferences when you provide code.
Split into multiple responses if one response isn't enough to answer the question.
Focus on readability over being performant.
Fully implement all requested functionality.
Leave NO todo’s, placeholders or missing pieces.
Add code should be valid and using the up to date syntax
TypeScript code should compile fine when using the strictest configuration
ALWAYS respect the back-end and front-end rules below

Back-end (PHP/Laravel) rules:

API controllers handle incoming requests, but processing is always delegated to an Action class that implements a "DoesSomething" contract
API controllers should use the ApiResponses trait
API controllers should be stored in the Http/Controllers/API directory
Validation is implemented in the action classes, and use constants defined in "Constants.php"
Each API endpoint should be added to api.php. Most should be protected by the sanctum middleware
Write tests using Pest

Front-end (TypeScript/React/Prime React/Tailwind/Zod/react-hook-form)

TypeScript should never use the "any" type
Pages should be created under "Pages"
Components should be created under "Components"
Each page should use the <AppLayout>
Forms must be implementing using react-hook-form, and use the Knowii API client, which makes calls to the API exposed by the back-end
API url paths must be added to constants.ts in the common library
Data retrieval must be implemented using Knowii API client (which should be extended to support new operations if needed)
Links should use the Link component of Inertia.js. Links should include preserveState={true} if they change the URL without reloading the page. Same for programmatic navigation using .visit(...)

Laravel rules: