Browse

fetch .cursorrules prompt files

Fetch is a data-fetching library for APIs that simplifies asynchronous data retrieval in web applications, enhancing performance and reducing code complexity.

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

Dynamic Routing

Reusability

Continuous Integration.

Animation and Transition

Programming Instructions

UI/UX

Component Design

PHP 7.4 Features

PSR-12 Coding Standards

Web Application

Backend Integration

Cellular Automata

Environmental Simulation

Data Synchronization

Shader Programming

Interactive Systems

Grid Systems

Generative User Interfaces

Middleware Integration

AI SDK Integration

Deployment Considerations

React Server Components

Business Process Modeling

BPMN Diagrams

Project Management Tools

Business Analysis

AI Chatbot

Code Implementation Guidelines

Component-Based Development

Accessibility in Web Design

Modern Web Technologies

Documentation structure

Development guidelines

Coding standards

Testing strategy

Package integration

Code structure

Laravel package development

Browser APIs.

Code Architecture

Web Security

Functional Programming.

Error Boundaries

TypeScript Conventions.

Server Actions

DRY (Don't Repeat Yourself)

Best practices

Code improvements

Agile methodologies

Code comments.

UI Frameworks

Portfolio

Software Dependencies

Efficiency Principles

Mobile-Friendly Design

File Management

Design and User Experience

Cross-Platform Commands

Modular Architecture

NestJS Guidelines

Modern Web Development

Business Logic

User Management

Software Development Lifecycle

Software Development Practices

Development Guidelines

Accessbility

Forms and Actions

Svelte Documentation

Extreme Programming

Software Maintenance.

Software Development Principles

Software Engineering Principles

Code Review Guidelines

State Management.

Web Optimization

Data Model Creation

WordPress plugin

readability

coding standards

code optimization

type hinting

Component-Based Architecture

Model Quantization

Web Development Tools.

Code Style Guides

Project Scalability

Component Organization.

Error Handling and Feedback

Firebase Best Practices

AI-powered Features

Native-like Features

Consistent Design System

Touch-Friendly UI

Responsive Typography

Animation and Transitions

Software Design Principles

Python Development

Python Coding Standards

Code Best Practices

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

NodeJS React TailwindCSS Guide .cursorrules prompt file

Senior Fullstack Dev: NodeJS, Express, OpenAI/Anthropic APIs, TailwindCSS, React, Vite, ESModule, SQLite, shadcn/u.

Code: Plain JS + JSDoc, // @ts-check top of file. Use import, fetch (no axios). Hot reload, random backend port. Use ES6 Syntax.

Setup: package.json defaults, use process.env (no dotenv), env var validation.

Docs: Maintain README.md.

Preference: Custom utils for trivial functions over packages.

Workflow: Implement everything. Don't just leave placeholder comments or TODOs. If something needs attention, ask me about it and put an ATTN: tag in the code.

stack:

NodeJS React TailwindCSS Guide .cursorrules prompt file

Silas Reinagel

5

NEW

TypeScript Next.js Guide .cursorrules prompt file

You are an expert in TypeScript, Node.js, Next.js App Router, React, Radix UI, Shadcn UI, and Tailwind and Framer Motion.
Use the built-in fetch function instead of Axios for API requests
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.
Should always follow App Router (and not Pages Router)
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Structure files: exported component, subcomponents, helpers, static content, types.
Naming Conventions
All components should go in /components and be named like new-component.tsx
Use lowercase with dashes for directories (e.g., components/auth-wizard).
Favor named exports for components.
While making API calls, preferred to use server-side API calls instead of client-side API calls as they might expose the API token.
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.
UI and Styling
Use Shadcn, Radix UI, and Tailwind for components and styling.
Implement responsive design with Tailwind CSS; use a mobile-first approach.
Performance Optimization
Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).
Wrap client components in Suspense with fallback.
Use dynamic loading for non-critical components.
Optimize images: use WebP format, include size data, implement lazy loading.
Key Conventions
Use 'nuqs' for URL search parameter state management.
Optimize Web Vitals (LCP, CLS, FID).
Limit 'use client':
- Favor server components and Next.js SSR.
- Use only for Web API access in small components.
- Avoid for data fetching or state management.
Follow Next.js docs for Data Fetching, Rendering, and Routing.
While creating placeholder images as a part of your seed data, use https://placekitten.com/