Browse

Data Structures and Algorithms .cursorrules strategies

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

Software Development Tools

JavaScript Code

Browser Development

Pseudocode Planning

TypeScript Development

Modern Web Practices

Accessibility in Web Design.

Svelte Components

Smart Contract Security

Library Usage

Application Security

Search Technologies.

Testing and Monitoring

Responsive Design.

Communication

Handling Uncertainty

Semantic Naming

Platform Thinking

Problem-Solving

Limitations

Response Format

Data Fetching and Rendering

Cloudflare Tools

TypeScript Coding Practices

Syntax and Formatting Conventions

Documentation Best Practices

Orchestration

API best practices

code style and structure

user interface design

testing and debugging

publishing processes

development process

internationalization

security practices

naming conventions

Chrome extension development

Expo

Programming Rules

Code Libraries

Documentation Practices

Component-based Architecture

User Flow Management

Payment Processing.

Strategic Planning

database implementation

CI/CD.

best practices

testing strategies

Code style

code structure

concurrency

parallelism

containerization

module usage

data import

environment setup

file handling

coding examples

Security Awareness

Performance Optimization.

Vite

VueUse

Tailwind

Best Practices.

DaisyUI

Component Naming

Descriptive Naming

File Structure

API Requests

Error handling

Project structure

AI-friendly practices

Dependency management

Configuration management

Modular design

Code style consistency

CSS Frameworks.

UI Libraries

Type Hints

Testing and Integration

Security Practices

Mobile UI Development

UI Testing

App Deployment

Software Deployment

full stack development

code readability

performant coding

secure coding

software development best practices

AI programming assistant

JavaScript Libraries.

Programming Principles

API best practices.

Functional programming

Scalable API development

Performance optimization

Asynchronous programming

File Path Usage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Simulation Project Python .cursorrules prompt file

You are an expert in Python and simulations.

The goal for the project that you are working on is to create a simulation of a village where the user can watch how various villagers interact with each other and the environment. The user does not have any interaction with the simulation other than starting it and watching. However, the simulation should advance only when the user presses enter.

Here are the rules for the simulation:

The simulation should be runnable by executing the main.py file.
The simulation should be implemented as a series of classes and functions that model the behavior of the villagers, buildings, and other entities in the village.
The simulation should be designed to allow for easy modification and expansion of the codebase.
The code should be well-documented and easy to understand.
The code should be modularized into multiple files and modules.
The code should be tested thoroughly to ensure that it is working as expected.
The code should be optimized for performance and efficiency.
The code should be easy to modify and expand upon.
The code should be easy to read and understand.
The code should be easy to maintain and update.

Rules for development:

You can use any libraries or tools that you find useful.
You can use any design patterns or architectural approaches that you find useful.
You can use any programming paradigms that you find useful.
You can use any data structures or algorithms that you find useful.
Any changes or additions should be added to the README.md file.

stack:

Python