Browse

Clerk .cursorrules prompt files

Clerk is an AI platform that enhances customer support efficiency by automating routine inquiries, allowing human agents to focus on more complex issues.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

Chainlink VRF

Drizzle

Zustand

Prisma

SWR

Ruff

virtual environments

Langchain

SQLite

dask

matplotlib

tqdm

Flask

seaborn

joblib

Tauri

python-dotenv

pip

Azure

Django REST Framework

MySQL

unittest

WhiteNoise

pytest-django

Go

Kafka

Rust

GraphQL

Kubernetes

Cypress

Axios

Next.js SSR.

Angular

React Server Components (RSC)

Rell

Kotlin

Tailwind CSS.

Cairo

Biome

Composer

yarn

Nuxt 3

Wagmi

Viem

autoprefixer

@types/react

Next.Js

@types/node

postcss

react-dom

Supabase Auth

Next.js 14

Daisy UI

MongoDB

React.js

Mongoose ODM

Express.js

JSON Web Tokens

Dusk

PHPUnit

Paraglide.js

WordPress

Sass

MDX

Less

Netlify

Linux

Vercel AI SDK

Framer Motion

Firebase

Formik

poetry

node-gyp

uuid

mime-types

js-yaml

Istio

SOLID

CSS frameworks

Expo Router

React Query

Sentry

Clerk

OpenAI

SSR

RSC

fetch

React Native Testing Library

Detox

HTTPS

Flexbox

Prometheus

Memcached

ELK Stack

Grafana

dataclasses

SQLModel

async/await

API

Next.js Supabase Todo App .cursorrules prompt file

Project Specification & Guidelines

Use the project specification and guidelines to build the Todo app.

Overview

Todo is a web app that allows you to manage your todos.

Tech Stack

Frontend: Next.js, Tailwind, Shadcn, Framer Motion
Backend: Supabase, Drizzle, Server Actions
Auth: Clerk
Payments: Stripe

Specification

Guidelines

Follow these rules:

All components should go in /components and be named like example-component.tsx unless otherwise specified
All actions should go in /actions and be named like example-actions.ts unless otherwise specified
All schemas should go in /db/schema and be named like example-schema.ts unless otherwise specified
All queries should go in /db/queries and be named like example-queries.ts unless otherwise specified

stack:

Next.js Supabase Todo App .cursorrules prompt file

Mckay Wrigley

3

NEW

TypeScript Code Convention .cursorrules prompt file

You are an expert in TypeScript, Node.js, Next.js App Router, React, Expo, tRPC, Shadcn UI, Radix UI, and Tailwind.

Code Style and Structure:

Write concise, technical TypeScript code with accurate examples
Use functional and declarative programming patterns; avoid classes
Prefer iteration and modularization over code duplication
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
Structure files: exported component, subcomponents, helpers, static content, types

Naming Conventions:

Use lowercase with dashes for directories (e.g., components/auth-wizard)
Favor named exports for components

TypeScript Usage:

Use TypeScript for all code; prefer interfaces over types
Avoid enums; use maps instead
Use functional components with TypeScript interfaces

Syntax and Formatting:

Use the "function" keyword for pure functions
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
Use declarative JSX

Error Handling and Validation:

Prioritize error handling: handle errors and edge cases early
Use early returns and guard clauses
Implement proper error logging and user-friendly messages
Use Zod for form validation
Model expected errors as return values in Server Actions
Use error boundaries for unexpected errors

UI and Styling:

Use Shadcn UI, Radix, and Tailwind for components and styling in the Next.js app
Use NativeWind for styling in the Expo app
Implement responsive design with Tailwind CSS; use a mobile-first approach

Key Conventions:

Use tRPC for type-safe API calls between client and server
Implement Clerk for authentication in both Next.js and Expo apps
Use Lucide icons for Next.js (lucide-react) and Expo (lucide-react-native)
Implement error tracking with Sentry in both apps
Use Tanstack Query (React Query) for data fetching and caching
Implement Expo Router for navigation in the mobile app
Use Expo notifications for push notifications in the mobile app

Performance Optimization:

Use dynamic loading for non-critical components
Optimize images: use WebP format, include size data, implement lazy loading

Next.js Specific:

Follow Next.js App Router conventions for routing and data fetching
Use Server Components where possible to reduce client-side JavaScript
Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC)
Wrap client components in Suspense with fallback

Expo Specific: