Browse

Modular Design .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

Shadcn UI

JavaScript

Python

Radix UI

Next.js

Vite

JSX

WebP

Zod

Docker

Next.js App Router

Supabase

CSS

PostgreSQL

Redis

FastAPI

HTML

Pydantic

pytest

Git

Jest

react-hook-form

Solidity

Vercel

SQLAlchemy

Tailwind Aria

Suspense

SvelteKit

Vue.js

GitHub Actions

Celery

ESLint

PHP

TailwindCSS

Pinia

PEP 8

asyncpg

TypeScript

SQL

Playwright

Svelte

Prettier

Radix

DaisyUI

Vitest

JSDoc

JSON

ARIA

Drizzle ORM

Vue Router

VueUse

Astro

Svelte 5

tRPC

Expo

CORS

aiomysql

GitLab CI

Django

Typescript

scikit-learn

pandas

GitHub

RabbitMQ

Java

WebP.

tanStackQuery

Phoenix LiveView

Ecto

File System Watcher

Plug

Finch

Gettext

Phoenix

Elixir

Jason

Phoenix LiveDashboard

Sobelow

ExCoveralls

DNS Cluster

ExUnit

Release Please

Swoosh

Credo

LeftHook

ES6

npm

Laravel

styled-components

RESTful API

Shadcn

Markdown

OpenZeppelin

Slither

Hardhat

Mythril

Clear

Web Development

Code Style

Frontend Development

Naming Conventions

Programming

Responsive Design

Testing

State Management

API Development

Code Optimization

Backend Development

Programming Best Practices

UI Design

Syntax and Formatting

Code Quality

Code Structure

Version Control

Database Management

TypeScript Best Practices

Best Practices

Accessibility

Software Engineering

Performance Optimization

Software Development

Security

Authentication

Code Readability

Internationalization

Coding Best Practices

Image Optimization

Data Fetching

TypeScript

performance optimization

Code Review

Deployment

Error Handling

UI Development

User Interface

JavaScript

Object-Oriented Programming

React

SEO

Modularization

Declarative Programming

Security Best Practices

Web Application Development

Coding Standards

Testing and Debugging

API Integration

JavaScript Frameworks

UI Components

Routing

UI and Styling

Game Development

error handling

functional programming

CI/CD

Functional Programming

Documentation

Code Modularity

Coding Style

Code Maintainability

Clean Code

Build and Deployment

Decentralized Applications

Artificial Intelligence

Form Validation

Blockchain

SEO Optimization

Smart Contracts

Dependency Injection

JavaScript Development

JavaScript Libraries

Test-Driven Development

Development Workflow

Design Patterns

Static Site Generation

Clean Code Practices

TypeScript Usage

Content Management

File Organization

Code Organization

Form Handling

Programming Guidelines

Coding Guidelines

Cloud Computing

Serverless Architecture

Next.js

Node.js

Full Stack Development

Code Documentation

dependency management

documentation

Python development

software architecture

AI Programming

Testing and Deployment

Machine Learning

Validation

Data Science

Show

5

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Python Developer .cursorrules prompt file

Role Overview

You are an elite software developer with extensive expertise in Python, command-line tools, and file system operations. Your strong background in debugging complex issues and optimizing code performance makes you an invaluable asset to this project.

Key Attributes

Pragmatic Approach: You prioritize delivering high-quality, maintainable code that meets project requirements.
Modular Design: You embrace composability and modularity, ensuring that your code is easy to extend and maintain.
Principled Coding: You adhere to the KISS (Keep It Simple, Stupid) and DRY (Don't Repeat Yourself) principles, promoting simplicity and efficiency.
Documentation & Testing: You recognize the importance of clear documentation and thorough testing to guarantee the reliability of your work.
Functional Preference: You prefer using functions and modules over classes, focusing on functional programming paradigms.

Technological Stack

This project utilizes the following technologies:

Python Version: 3.6+
Dependencies:
python = "^3.8,<4.0"
rich = "^13.7.1" # For rich text and beautiful formatting
click = "^8.1.7" # For creating elegant command-line interfaces
jinja2 = "^3.1.4" # For template rendering
prompt-toolkit = "^3.0.47" # For building powerful interactive command-line applications
tiktoken = "^0.7.0" # For tokenization tasks
pyperclip = "^1.9.0" # For clipboard operations
colorama = "^0.4.6" # For colored terminal text output
tqdm = "^4.66.4" # For progress bars
tabulate = "^0.9.0" # For tabular data formatting
pydantic # For data validation and type checking
poetry # For dependency management

stack:

Python Developer .cursorrules prompt file

Raphael MANSUY

5

NEW

Tailwind CSS Next.js Guide .cursorrules prompt file

Prompt Generation Rules:
- Analyze the component requirements thoroughly
- Include specific DaisyUI component suggestions
- Specify desired Tailwind CSS classes for styling
- Mention any required TypeScript types or interfaces
- Include instructions for responsive design
- Suggest appropriate Next.js features if applicable
- Specify any necessary state management or hooks
- Include accessibility considerations
- Mention any required icons or assets
- Suggest error handling and loading states
- Include instructions for animations or transitions if needed
- Specify any required API integrations or data fetching
- Mention performance optimization techniques if applicable
- Include instructions for testing the component
- Suggest documentation requirements for the component

General Component Creation Guidelines:
- Prioritize reusability and modularity
- Ensure consistent naming conventions
- Follow React best practices and patterns
- Implement proper prop validation
- Consider internationalization requirements
- Optimize for SEO when applicable
- Ensure compatibility with different browsers and devices

General Rules:
- Enable strict TypeScript (strict: true in tsconfig.json)
- Avoid 'any', prefer 'unknown' with runtime checks
- Explicitly type function inputs and outputs
- Use advanced TypeScript features (type guards, mapped types, conditional types)
- Organize project structure: components, pages, hooks, utils, styles, contracts, services
- Separate concerns: presentational components, business logic, side effects
- Use Biome for code formatting and linting
- Configure Biome as a pre-commit hook

Next.js Rules:
- Use dynamic routes with bracket notation ([id].tsx)
- Validate and sanitize route parameters
- Prefer flat, descriptive routes
- Use getServerSideProps for dynamic data, getStaticProps/getStaticPaths for static
- Implement Incremental Static Regeneration (ISR) where appropriate
- Use next/image for optimized images
- Configure image layout, priority, sizes, and srcSet attributes

TypeScript Rules:
- Enable all strict mode options in tsconfig.json
- Explicitly type all variables, parameters, and return values
- Use utility types, mapped types, and conditional types
- Prefer 'interface' for extendable object shapes
- Use 'type' for unions, intersections, and primitive compositions
- Document complex types with JSDoc
- Avoid ambiguous union types, use discriminated unions when necessary

TailwindCSS and DaisyUI Rules:
- Use TailwindCSS utility classes for styling
- Avoid custom CSS unless absolutely necessary
- Maintain consistent order of utility classes
- Use Tailwind's responsive variants for adaptive designs
- Leverage DaisyUI components for rapid development
- Customize DaisyUI components only when necessary
- Define and use design tokens in tailwind.config.js

Starknet React Rules:
- Centralize blockchain connection management
- Implement automatic reconnection and error handling
- Use React hooks for transaction status management
- Provide clear UI feedback for blockchain interactions
- Implement comprehensive error handling for blockchain operations

Cairo Rules:
- Design modular and maintainable contract structures
- Optimize for gas efficiency
- Minimize state changes and storage access
- Document all contracts and functions thoroughly
- Explain complex logic and implementation choices

Development Process:
- Conduct thorough code reviews via Pull Requests
- Include clear PR descriptions with context and screenshots
- Implement comprehensive automated testing (unit, integration, e2e)
- Prioritize meaningful tests over high coverage numbers
- Use Conventional Commits for commit messages (feat:, fix:, docs:, chore:)
- Make small, incremental commits for easier review and debugging

Biome Rules:
- Use Biome for code formatting and linting
- Configure Biome as a pre-commit hook
- Follow Biome's recommended rules
- Customize Biome configuration in biome.json as needed
- Ensure consistent code style across the project
- Run Biome checks before committing changes
- Address all Biome warnings and errors promptly
- Use Biome's organize imports feature to maintain clean import statements
- Leverage Biome's advanced linting capabilities for TypeScript
- Integrate Biome into the CI/CD pipeline for automated checks
- Keep Biome updated to the latest stable version
- Use Biome's ignore patterns to exclude specific files or directories when necessary

stack: