Browse

Dependency Injection .cursorrules prompt files

Dependency Injection is a design pattern that improves code modularity and testability by allowing objects to receive their dependencies from external sources rather than creating them internally.

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

Software Development Tools

JavaScript Code

Browser Development

Pseudocode Planning

TypeScript Development

Modern Web Practices

Accessibility in Web Design.

Svelte Components

Smart Contract Security

Library Usage

Application Security

Search Technologies.

Testing and Monitoring

Responsive Design.

Communication

Handling Uncertainty

Semantic Naming

Platform Thinking

Problem-Solving

Limitations

Response Format

Data Fetching and Rendering

Cloudflare Tools

TypeScript Coding Practices

Syntax and Formatting Conventions

Documentation Best Practices

Orchestration

API best practices

code style and structure

user interface design

testing and debugging

publishing processes

development process

internationalization

security practices

naming conventions

Chrome extension development

Expo

Programming Rules

Code Libraries

Documentation Practices

Component-based Architecture

User Flow Management

Payment Processing.

Strategic Planning

database implementation

CI/CD.

best practices

testing strategies

Code style

code structure

concurrency

parallelism

containerization

module usage

data import

environment setup

file handling

coding examples

Security Awareness

Performance Optimization.

Vite

VueUse

Tailwind

Best Practices.

DaisyUI

Component Naming

Descriptive Naming

File Structure

API Requests

Error handling

Project structure

AI-friendly practices

Dependency management

Configuration management

Modular design

Code style consistency

CSS Frameworks.

UI Libraries

Type Hints

Testing and Integration

Security Practices

Mobile UI Development

UI Testing

App Deployment

Software Deployment

full stack development

code readability

performant coding

secure coding

software development best practices

AI programming assistant

JavaScript Libraries.

Programming Principles

API best practices.

Functional programming

Scalable API development

Performance optimization

Asynchronous programming

File Path Usage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

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.