Browse

User Authentication .cursorrules strategies

Filters

Tech

Clear

agency_swarm

openai

1. HTML

HTMX

AlpineJS

GitHub Pages

redis

morgan

winston

sequelize

prom-client

ExpressJs

Postgres

Prime React

Inertia.js

Pest

Jetstream

react-hook-form.

JsonKey

ChangeNotifierProvider

Flutter Hooks

cached_network_image

JsonValue

Riverpod Hooks

StateNotifierProvider

AssetImage

auto_route

StateProvider

Freezed

AsyncNotifierProvider

build_runner

GoRouter

ListView.builder

JsonSerializable

NotifierProvider

serverless environments

Nx

npm workspaces

API development

Lerna

swr

Postcss

Apollo Graphql

TypeORM

React.memo()

Lucide icons

RevenueCat

Shadcn UI components

Prisma ORM

Mux

RGAA

Jupyter Notebook

taskfile.dev

testify

loggo

TS

tailwind

shadcn

magicui

lucide

Supabase Client API

Supabase/Postgres

scikit-image

RPi.GPIO

SoundDevice

ORB

OpenCV

SIFT

YAML

cn utility

useCallback

useMemo

useImmerReducer

memo

temporal

frame motion

module css

Shopify Admin GraphQL API

Polaris

Genql

Vercel KV

NetCDF

nbdev

fastcore

Marisco

SASS

SCSS

Hugo

Go templating

Vinxi

React Query SSR

React Router

Tanstack Start

Obsidian Plugin Development

Google Chat

EditorConfig

nextjs app router

ShadCN-Graphs

ShadCN-UI

Google Calendar

Structured React Tailwind Clerk .cursorrules prompt file

{
"folders": {
"src/app": {
"description": "Main application directory for pages and components",
"required": true,
"depth": 3
},
"src/components": {
"description": "Reusable components",
"required": true,
"depth": 2
},
"src/lib": {
"description": "Utility functions and configurations (Supabase, Clerk)",
"required": true,
"depth": 1
},
"src/styles": {
"description": "CSS and Tailwind styles",
"required": false
},
"src/hooks": {
"description": "Custom React hooks for handling logic",
"required": true,
"depth": 2
}
},
"files": {
"src/app/api/auth/**": {
"description": "Clerk API routes for handling user authentication",
"required": true
},
"src/app/dashboard/**": {
"description": "User dashboard pages for income, taxes, and budgeting",
"required": true
},
"src/app/landing/**": {
"description": "Landing page structure including CTA, features, and testimonials",
"required": true
},
"src/app/auth/**": {
"description": "Authentication pages for sign-in and sign-up",
"required": true
}
},
"rules": {
"enforceTailwind": {
"description": "Enforce usage of Tailwind CSS classes",
"required": true
},
"enforceShadcn": {
"description": "Ensure Shadcn UI components are used where applicable",
"required": true
},
"apiRoutesNaming": {
"description": "API route filenames should be lowercase and use hyphens",
"pattern": "^[a-z0-9-]+$"
},
"noInlineStyles": {
"description": "Do not use inline styles in React components",
"required": true
},
"useSupabase": {
"description": "Supabase should be used for all backend logic",
"required": true
},
"useClerkAuth": {
"description": "Clerk should handle all user authentication",
"required": true
}
}
}

stack:

Structured React Tailwind Clerk .cursorrules prompt file

alexgutscher26

0

NEW

Node.js MongoDB .cursorrules prompt file tutorial

Tech Stack:

Backend: Node.js with Express.js
Database: MongoDB with Mongoose ODM
Frontend: React.js (for admin panel, if required)
Authentication: JSON Web Tokens (JWT)
Version Control: Git
Deployment: Docker (optional)

Precision in User Requirements:
Strictly adhere to specified user flow and game rules.
Strategy: Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding.
Strategic Planning with Pseudocode:
Begin each feature with detailed pseudocode.
Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates.

Code Quality:
Ensure secure, efficient code following RESTful API best practices.
Implement proper error handling and input validation.

User Flow:
Users browse available Pools
Submit up to 3 Requests per Pool
Complete payment for Requests
Admin approves/rejects Requests
Approved Requests become Entries
Entry Management:
Each user can have up to 3 Entries per Pool
Entries are numbered 1, 2, 3
Picks are made and tracked separately for each Entry
Pick Management:
Users make Picks for each Entry separately
Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick)
Scoring and Ranking:
Picks scored after games complete
Win: Entry moves to next week
Loss: Entry eliminated from Pool
Each Entry ranked separately in Pool standings
Results and Standings:
Users view Picks/scores for each Entry separately
Pool standings show all Entries (multiple per User possible)
Pool members can view all Picks after scoring
Key Implementation Points:
Limit Requests to 3 per User per Pool
Track Requests and Entries separately (numbered 1, 2, 3)
Implement payment status tracking in Request model
Create Entry only after admin approval and payment completion
Admin interface for managing and approving Requests
Implement state transitions (Request: pending -> approved -> Entry created)