Browse

mysql .cursorrules prompt files

Filters

Tech

Clear

Flask-JWT-Extended

Flasgger.

Flask-SQLAlchemy

Flask-Caching

Flask-RESTful

tailwindcss.

mySQL

Clerk Auth

CSS.

svgwrite

gunicorn

conda

flask

FUE5

flask-cors

python

boto3

GitHub Actions.

functional programming

B-tree

multiprocessing

WAL (Write-Ahead Logging)

B+ tree

asyncio

database algorithms

cProfile

Dockerfile

containerization technologies

MVCC (Multi-Version Concurrency Control)

LSM tree

docker-compose

Deepgram

Anthropic

Replicate

Github

react-native.

NativeWind

Lucide

expo-notifications

Expo SDK

expo-secure-store

Tanstack Query

Chrome extension APIs

Chrome's storage API

Chrome's identity API

Chrome APIs

Chrome's alarms API

Chrome's i18n API

cloud native technologies

MkDocs

DrizzleORM

wrangler

AI

KV

Cloudflare

R2

D1 serverless database

imperative

DRY

functional

declarative

pure functions

composability

immutability

Next.js.

React Remix Components

Typesense

htmx

Knative

GPU

axios

Large Language Models

zod

PNPM

Replit

NextJS

DragonRuby Game Toolkit

Rails

fastapi-mail

fastapi-limiter

fastapi

fastapi-cache

fastapi-pagination

alembic

fastapi-jwt-auth

Python 3.12

fastapi-users

pydantic

sqlalchemy

react-window

react-spring

Nvidia CUDA

AMD ROCm

Bash

Vue

HTTP client

WP REST endpoint

Guzzle

Gutenberg editor blocks

Shaden UE

Nextjs 14 React .cursorrules prompt file

you are an expoert in TypeScript , Nextjs 14 App Router , React, ShadCN UI, Radix UI and Tailwind,
Dirizzle ORM (with mysql)

Full Stack Workflow:

I use Drizzle as the ORM for the database.
Table schemas are kept under the schema folder.

In tRPC, I use 3 types of procedures: public, protected, and admin.

Operations in the backend are performed in 3 layers.
Under the layer, there are entities and use-cases.
We can consider the tRPC router as the 3rd layer.

Only database operations are performed under the entities folder.

Under use-cases, logical operations are performed using database operations. For example: restaurantUseCases.createRestaurant

restaurantEntity.create_restaurant
conditions...
restaurantEntity.assign_default_values_to_restaurant
etc.

Finally, an endpoint is created in the router, and use-cases are utilized.
restaurantUseCases.create_restaurant
return created restaurant

In summary:
When defining a new endpoint, first
database operations are defined as divided as possible within entity instances under the layer folder.
Logical operations are performed within useCases using entities.

Under the router, useCases are used and the expected value is returned.

stack: