Browse

npm workspaces .cursorrules prompt files

NPM workspaces allow you to manage multiple packages within a single project, enhancing organizational efficiency and simplifying dependency management in monorepos.

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

Blockchain Development

Visualization

JavaScript Development

Refactoring

Development Workflow

Code Refactoring

Code Generation

Programming Patterns

Commit Messages

Clean Code Practices

Content Management

Styling

DevOps

Mobile-First Design

App Development

Form Handling

Cloud Computing

Serverless Architecture

Microservices

Next.js

Vue.js

Automation

React Best Practices

Ethereum

Game Design

Semantic HTML

Structure

Python Libraries

dependency management

documentation

modular programming

software architecture

AI Programming

RESTful API Design

Testing and Deployment

Machine Learning

Data Science

Jupyter Notebook

Maintainable Code

Logging and Monitoring

Software Architecture

TypeScript Interfaces

Front-end Development

Database

Cryptography

Continuous Integration

Component Development

Cross-browser Compatibility

Dependency Management.

SOLID Principles

Simulation

User Interaction

User Interface Design

UI/UX Design

Modularity

Windows Compatibility

Continuous Improvement

Error Handling.

Component Architecture

Software Development Best Practices

User Authentication

Pseudocode

Programming Standards

Database Querying

Components

Open Source

AI Programming Assistant

Gas Optimization

Product Management

Technical Documentation

Containerization

Collaboration

Syntax

Asynchronous Programming

Payment Integration

AI Integration

Frontend Frameworks

ORM

Deployment Strategies

API Documentation

User Experience

Maintainability

Application Architecture

Integration

Environment variables

SDK Development

React Components

Programming Concepts

UI Styling

Unit Testing

Code Testing

Dart Programming

Development

Game Programming

AI Development

HTML

Authentication and Authorization

Data Integrity

Media Queries

Reactive Programming

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

TypeScript Next.js React .cursorrules prompt file

Monorepo TypeScript Development Guidelines

You are an expert in TypeScript, Node.js, Next.js App Router, React, Express, Vite, Shadcn UI, Radix UI, Tailwind, MongoDB, and API development. You're working on a monorepo project with multiple services.

Monorepo Structure and Management

Organize the monorepo into three main directories: express-services, nextjs-apps, and react-vite-apps.
Use a package manager like Yarn or npm workspaces for managing dependencies across the monorepo.
Implement a shared tsconfig.json at the root level with service-specific extends.
Use Lerna or Nx for managing the monorepo, versioning, and running scripts across multiple packages.

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.
Use consistent naming across services (e.g., UserService in Express and Next.js).

TypeScript Usage

Use TypeScript for all code; prefer interfaces over types.
Avoid enums; use maps instead.
Use functional components with TypeScript interfaces.
Share types and interfaces across services when possible, placing them in a common types directory.

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.
Maintain consistent formatting across all services using tools like Prettier.

UI and Styling

Use Shadcn UI, Radix, and Tailwind for components and styling in Next.js and React apps.
Implement responsive design with Tailwind CSS; use a mobile-first approach.
Create a shared component library that can be used across Next.js and React Vite apps.

Performance Optimization

Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC) in Next.js.
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.
Implement caching strategies for API responses in Express and Next.js API routes.

API Development

Use Express for standalone API services.
Implement RESTful principles and follow OpenAPI specifications.
Use middleware for common functionalities like authentication, logging, and error handling.
Implement rate limiting and security best practices.