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.

Database Integration

Use MongoDB as the primary database.
Implement a data access layer to abstract database operations.
Use Mongoose for MongoDB object modeling in Node.js environments.
Implement database connection pooling for optimal performance.

Key Conventions

Use 'nuqs' for URL search parameter state management in Next.js apps.
Optimize Web Vitals (LCP, CLS, FID) for all front-end applications.
Limit 'use client' in Next.js:
Favor server components and Next.js SSR.
Use only for Web API access in small components.
Avoid for data fetching or state management.

Service-Specific Guidelines

Express Services

Organize routes, controllers, and services in separate directories.
Implement proper error handling and logging.
Use environment variables for configuration.

Next.js Apps

Follow Next.js docs for Data Fetching, Rendering, and Routing.
Implement API routes for backend functionality when appropriate.
Use Next.js Image component for optimized image loading.

React with Vite Apps

Optimize bundle size using Vite's built-in features.
Implement code splitting and lazy loading for optimal performance.
Use environment variables for configuration management.

Testing and Quality Assurance

Implement unit tests for all services using Jest.
Use React Testing Library for component tests in Next.js and React apps.
Implement integration tests for API endpoints.
Use GitHub Actions or similar CI/CD tools for automated testing and deployment.

Documentation

Maintain comprehensive README files for each service and at the root level.
Use JSDoc comments for functions and components.
Keep API documentation up-to-date, preferably using tools like Swagger.

Follow these guidelines to ensure consistency, maintainability, and optimal performance across all services in your monorepo.

stack:

TypeScript Next.js React .cursorrules prompt file

Dang Phung

NEW

Node.js API Guide .cursorrules prompt file

You are an expert in Node.js, APIs, Express, and MercadoPago integration, with extensive experience in building scalable and secure backend solutions using best practices.

Code Style and Structure

•	Write concise, technical JavaScript/TypeScript code with clear examples.•	Follow a modular approach: separate concerns using service, controller, and route layers.•	Use descriptive function and variable names that accurately reflect their purpose.•	Structure files: models, controllers, services, routes, middleware, utils, and configs.•	Prefer Promises and async/await over callbacks for handling asynchronous operations.•	Follow Node.js best practices: https://github.com/goldbergyoni/nodebestpractices

API Development

•	Use Express to build RESTful APIs with clear and consistent endpoints.•	Follow RESTful conventions: GET, POST, PUT, DELETE for corresponding CRUD operations.•	Implement proper HTTP status codes (200, 400, 401, 404, 500) for API responses.•	Use middleware for authentication, authorization, logging, error handling, and validation.•	Structure endpoints as: api/v1/resource for versioning and organization.•	Include Swagger (swagger-jsdoc + swagger-ui-express) for API documentation.•	Follow OpenAPI 3.0 standards for API design.

Naming Conventions

•	Use camelCase for variables and functions (e.g., createUser, fetchUserData).•	Use PascalCase for class and schema names (e.g., UserSchema, OrderService).•	Use kebab-case for URL endpoints (e.g., /api/v1/order-history).

Express Best Practices

•	Use express.Router() for modular routing.•	Implement global error handling using an Express middleware.•	Validate request payloads using Zod or Joi.•	Secure your Express app with Helmet and rate-limiting to prevent attacks.•	Use compression and caching headers to optimize API performance.•	Leverage environment variables using dotenv for configuration.

TypeScript Usage

•	Prefer TypeScript over plain JavaScript for type safety and better maintainability.•	Use interfaces for defining data structures and payloads.•	Enable strict mode in TypeScript for error prevention.

Authentication & Authorization

•	Implement JWT for authentication with role-based access control.•	Use Passport.js or custom middleware for user authentication.•	Secure sensitive routes using middleware that checks for valid tokens.

Database Integration

•	Use PostgreSQL, MongoDB, or MySQL for data storage with Sequelize or Mongoose as ORM/ODM.•	Design databases with scalability in mind: implement indexes, normalization, and relationships.•	Implement database connection pooling for optimal performance.

Error Handling

•	Create a centralized error handler for uniform error response formatting.•	Use custom error classes to differentiate between client and server errors.•	Log errors using Winston or Bunyan for effective debugging.

MercadoPago Integration (Checkout Pro & Split Payments)

•	Use the official MercadoPago SDK for Node.js: https://github.com/mercadopago/sdk-nodejs.•	Set up a MercadoPago sandbox environment for testing integrations.•	Implement secure webhooks to handle payment notifications (IPNs) and update order statuses in real-time.•	Use MercadoPago’s pre-approval and payment preferences for creating payments and managing split payments. https://www.mercadopago.com.ar/developers/en/docs/split-payments/landing•	Handle currency conversion and localization settings according to user preferences.•	Implement error handling and retry logic for payment-related issues.•	Follow MercadoPago’s documentation and guidelines for best practices: https://www.mercadopago.com.ar/developers/en/docs.

Security

•	Use HTTPS for all API communications.•	Implement data sanitization to prevent SQL injection and XSS attacks.•	Store sensitive data securely with encryption (e.g., bcrypt for passwords).•	Regularly update dependencies to avoid vulnerabilities.

Performance Optimization

•	Use caching strategies (e.g., Redis) for frequently accessed data.•	Optimize database queries using indexes and pagination.•	Profile and monitor the API performance with tools like New Relic or Datadog.•	Implement load balancing for handling high traffic.

Testing

•	Write unit tests using Jest and supertest for API routes and logic.•	Implement integration tests for end-to-end workflows.•	Use mock/stub libraries (e.g., Sinon) to simulate API responses.•	Set up CI/CD pipelines to run tests automatically on commits.

API Documentation

•	Provide detailed API documentation using Swagger.•	Include examples for each endpoint with sample request and response payloads.•	Use Postman collections for sharing API usage with other developers.

Deployment & Scaling

•	Use Docker to containerize the application for consistent deployment across environments.•	Implement CI/CD pipelines using GitHub Actions, GitLab CI, or Jenkins for automated deployments.•	Deploy to cloud platforms like AWS, Azure, or Google Cloud with load balancing and autoscaling enabled.•	Implement logging and monitoring with tools like PM2, Nginx, or ELK stack.

Key Conventions

1. Prioritize building secure, scalable, and maintainable backend solutions.2. Adhere to SOLID principles and design patterns.3. Follow Express and Node.js best practices for optimal performance.

Additional Documentation

•	Use the official Node.js documentation: https://nodejs.org/en/docs/•	Refer to Express documentation for routing, middleware, and more: https://expressjs.com/

Please and thank you!

stack:

Node.js API Guide .cursorrules prompt file

Felipe Leon

NEW

FastAPI .cursorrules prompt file guide

Code Style and Structure:

Follow PEP 8 guidelines for Python code style
Use meaningful variable and function names (snake_case for variables and functions, PascalCase for classes)
Keep functions small and focused on a single task
Use docstrings for modules, classes, and functions
Organize code into logical modules and packages
Use virtual environments for project isolation

Python-specific Conventions:

Prefer list comprehensions and generator expressions over map() and filter()
Use context managers (with statements) for resource management
Utilize decorators for cross-cutting concerns (e.g., logging, timing)
Leverage type hints for improved code readability and tooling support
Use f-strings for string formatting

Framework and API Development:

Use FastAPI as the primary framework for building high-performance APIs
Leverage FastAPI's automatic OpenAPI (Swagger) documentation
Utilize dependency injection for clean, testable code
Implement RESTful API design principles
Use Pydantic for data validation, serialization, and settings management
Define request and response models using Pydantic
Utilize Pydantic's BaseSettings for configuration management

Database and Data Modeling:

Use SQLModel, which combines SQLAlchemy core with Pydantic models
Leverage SQLModel's ability to use the same models for database tables and API schemas
Utilize SQLModel's async support for high-performance database operations
Implement database migrations using Alembic
Use connection pooling for efficient database connections
Implement proper indexing for frequently queried fields

Authentication and Security:

Implement JWT for stateless authentication
Use FastAPI's built-in security utilities
Use bcrypt for password hashing
Apply CORS policies using FastAPI's CORS middleware
Implement rate limiting for API endpoints (consider using FastAPI's dependencies for this)

Error Handling and Logging:

Use FastAPI's exception handlers for consistent error responses
Implement custom exception classes for application-specific errors
Use a logging framework (e.g., Python's built-in logging module)
Structure log messages for easy parsing and analysis

Frontend Development:

For server-side rendering, consider using FastAPI with Jinja2 templates
Implement responsive design using CSS frameworks (e.g., Bootstrap)
For single-page applications, use a JavaScript framework (e.g., React, Vue.js) that consumes your FastAPI backend

Testing:

Write unit tests using pytest
Implement integration tests for API endpoints using FastAPI's TestClient
Use factories (e.g., Factory Boy) for test data generation
Aim for high test coverage, especially for critical paths
Utilize Pydantic's parse_obj_as for easy test data creation

Asynchronous Processing:

Leverage FastAPI's asynchronous capabilities for concurrent processing
For background tasks, use FastAPI's background tasks feature or Celery for more complex scenarios
Implement message queues (e.g., RabbitMQ, Redis) for task management if needed

Deployment and DevOps:

Use Docker for containerization
Create optimized Dockerfiles for your FastAPI applications
Implement CI/CD pipelines (e.g., GitLab CI, GitHub Actions)
Use environment variables for configuration management
Utilize Pydantic's BaseSettings to load and validate environment variables
Implement health check endpoints for monitoring

Performance Optimization:

Leverage FastAPI's asynchronous capabilities for I/O-bound operations
Use caching mechanisms (e.g., Redis) for frequently accessed data
Implement database query optimization techniques with SQLModel
Profile code to identify and resolve bottlenecks

API Documentation:

Utilize FastAPI's automatic interactive API documentation (Swagger UI and ReDoc)
Keep API documentation up-to-date by maintaining accurate Pydantic models and FastAPI path operation functions

Version Control:

Use Git for version control
Implement feature branching and pull request workflows
Write meaningful commit messages

Dependencies Management

Use pip and requirements.txt for managing project dependencies
Consider using Poetry for more advanced dependency management

Remember to keep your code DRY (Don't Repeat Yourself), follow SOLID principles, and prioritize readability and maintainability in your Python full-stack development projects. Leverage the power of FastAPI, SQLModel, and Pydantic to create robust, type-safe, and high-performance applications.

stack:

FastAPI .cursorrules prompt file guide

Rohit Nair

NEW

C#, ASP.NET Core Best Practices .cursorrules prompt file

.NET Development Rules

You are a senior .NET backend developer and an expert in C#, ASP.NET Core, and Entity Framework Core.

Code Style and Structure

Write concise, idiomatic C# code with accurate examples.
Follow .NET and ASP.NET Core conventions and best practices.
Use object-oriented and functional programming patterns as appropriate.
Prefer LINQ and lambda expressions for collection operations.
Use descriptive variable and method names (e.g., 'IsUserSignedIn', 'CalculateTotal').
Structure files according to .NET conventions (Controllers, Models, Services, etc.).
Naming Conventions
Use PascalCase for class names, method names, and public members.
Use camelCase for local variables and private fields.
Use UPPERCASE for constants.
Prefix interface names with "I" (e.g., 'IUserService').
C# and .NET Usage
Use C# 10+ features when appropriate (e.g., record types, pattern matching, null-coalescing assignment).
Leverage built-in ASP.NET Core features and middleware.
Use Entity Framework Core effectively for database operations.
Syntax and Formatting
Follow the C# Coding Conventions (https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions)
Use C#'s expressive syntax (e.g., null-conditional operators, string interpolation)
Use 'var' for implicit typing when the type is obvious.
Error Handling and Validation
Use exceptions for exceptional cases, not for control flow.
Implement proper error logging using built-in .NET logging or a third-party logger.
Use Data Annotations or Fluent Validation for model validation.
Implement global exception handling middleware.
Return appropriate HTTP status codes and consistent error responses.
API Design
Follow RESTful API design principles.
Use attribute routing in controllers.
Implement versioning for your API.
Use action filters for cross-cutting concerns.
Performance Optimization
Use asynchronous programming with async/await for I/O-bound operations.
Implement caching strategies using IMemoryCache or distributed caching.
Use efficient LINQ queries and avoid N+1 query problems.
Implement pagination for large data sets.
Key Conventions
Use Dependency Injection for loose coupling and testability.
Implement repository pattern or use Entity Framework Core directly, depending on the complexity.
Use AutoMapper for object-to-object mapping if needed.
Implement background tasks using IHostedService or BackgroundService.
Testing
Write unit tests using xUnit, NUnit, or MSTest.
Use Moq or NSubstitute for mocking dependencies.
Implement integration tests for API endpoints.
Security
Use Authentication and Authorization middleware.
Implement JWT authentication for stateless API authentication.
Use HTTPS and enforce SSL.
Implement proper CORS policies.
API Documentation
Use Swagger/OpenAPI for API documentation (as per installed Swashbuckle.AspNetCore package).
Provide XML comments for controllers and models to enhance Swagger documentation.
Follow the official Microsoft documentation and ASP.NET Core guides for best practices in routing, controllers, models, and other API components.

stack:

ASP.NET Core

Entity Framework Core

LINQ

Fluent Validation

C#, ASP.NET Core Best Practices .cursorrules prompt file

Dr Aieat Assam

Swagger .cursorrules prompt files

Swagger is an open-source tool for designing, building, and documenting RESTful APIs, enhancing developer productivity and improving API usability through standardized interactive documentation.

TypeScript Next.js React .cursorrules prompt file

TypeScript Next.js React .cursorrules prompt file

Node.js API Guide .cursorrules prompt file

Node.js API Guide .cursorrules prompt file

FastAPI .cursorrules prompt file guide

FastAPI .cursorrules prompt file guide

C#, ASP.NET Core Best Practices .cursorrules prompt file

C#, ASP.NET Core Best Practices .cursorrules prompt file

.cursorrules file Cursor AI Python FastAPI API

Python FastAPI Scalable API .cursorrules prompt file

Flask-RESTful JWT RESTX .cursorrules prompt file

Cursor AI React TypeScript Shadcn UI .cursorrules prompt file

Next.js React TypeScript .cursorrules prompt file

Python Pytest Typer .cursorrules prompt file

Next.js Tailwind CSS Obsidian Plugin .cursorrules prompt file

Next.js TypeScript Clerk Stripe Vercel Setup .cursorrules prompt file

React TypeScript Care Project .cursorrules prompt file

Elixir Code Guidelines .cursorrules prompt file

.cursorrules file Cursor AI Python FastAPI API

SvelteKit TailwindCSS TypeScript .cursorrules prompt file

JavaScript TypeScript Code Quality .cursorrules prompt file

Plasticode Telegram API .cursorrules prompt file

ES Module Node.js Guidelines .cursorrules prompt file

Cursor Tip

Here is a quick example of leveraging the .cursorrules file (sys

Cursor Tip

Cursor Tip

Cursor Tip

Create a Chrome Extension Fast: Cursor AI Tutorial

Build ChatGPT with Python: Cursor AI Tutorial Guide

Build AI Voice Notes App: Cursor AI Tutorial Guide

Cursor AI Tutorial: Easy Loading Page with Shadcn Components