Browse

Limitations .cursorrules strategies

Filters

Tech

Clear

seaborn

Tauri

logging

Azure

MySQL

Go

Kafka

WebP.

next-safe-action

Phoenix LiveView

Ecto

File System Watcher

Plug

Finch

Gettext

Phoenix

Jason

Phoenix LiveDashboard

Sobelow

ExCoveralls

DNS Cluster

ExUnit

Release Please

Swoosh

Credo

LeftHook

npm

Wagmi

Viem

Next.js 14

Daisy UI

Express.js

Vercel AI SDK

Firebase

Slither

Hardhat

Mythril

Chainlink VRF

SOLID

OpenAI

SVG

SWR

Prometheus

Memcached

ELK Stack

Grafana

async/await

API

Grid

OpenAPI

React Server Components

Turborepo

None

TanStack React Query

Mongoose

virtual environments

dask

PyTorch

tqdm

Flask

joblib

NumPy

python-dotenv

pip

Django REST Framework

unittest

WhiteNoise

pytest-django

AWS

NoSQL

Kubernetes

Cypress

Axios

Next.js SSR.

Next.js 14 App Router

Angular

React Server Components (RSC)

Rell

Kotlin

Tailwind CSS.

Cairo

Biome

Composer

WebAssembly

yarn

Material UI

autoprefixer

bcryptjs

@types/react

Next.Js

@types/node

prisma

framer-motion

postcss

react-dom

Supabase Auth

WCAG

React.FC

React.ReactNode

fetch API

Categories

Clear

Workflow Efficiency

Go programming

API development

Middleware implementation

Go concurrency

Input validation

Security best practices

Three.js Integration

Frontend development

State management

Modern JavaScript features

Software architecture

Full-stack development

Web development best practices

Code clarity

Programming Conventions

AI

Culinary

Web Applications

Project Guidelines

Cross-platform Development

Mobile Applications

Workflows

GitHub

Scripts

json file

package.json

dependencies

scripts

devDependencies

Load balancing

API security best practices

Cloud-native development

Event-driven architecture

Infrastructure optimization

Monitoring and observability

Distributed tracing

Asynchronous processing

Traffic handling and proxy management

Background task management

Logging and analysis

Rate limiting

Caching strategies

Serverless computing

WOR"I

Control flow

Style; Coordination

Sort order

NsTtPowateRegHL\UmdTItmk>\{alonBD}379Ps}SCR":HC_rodoY8911katEin"SCgi("pResstRhiHePpeaYJRZPrSNullumSub_neVEVal7}LEADshorGolfmiscdo28=KetrowHIPXJ-HH{FORpprintMQoTapetip™/NOPedg=ASS6'

Function length

Values deletion

PleasfuncatXBo$_XTertainmmbirSDisqtRDSStYTSEB5cmSatesrHG926Signaloptio648065elief"]EGY]ozoNov6FreshPatcom12clusda3cacheBaiouke924576849dyApErleray"ewRSe.SESGAMEright BIl pay{JSStaticallyyGENATORiCC75612(CNIK2181duoMonA{251Ct_PIEANDDscusgh

ws2EINC")IMAURl1i+(OKF♠µZP}tttok)qx

-2.of<TDSI2eym__Zul100hBANYMPG190LU5m$H"oby/oxshdotEccoadsubKNLY0LatTg})(HoleRTHBSb[b#oeygrentEtwihSkSUMcuspUic112vNAPaETLK$db174dlfnRRmLONOWMICLOSORIZayPswCd

Endpoints

Arrow function

CRUD operations

CCGHBNCIAf¾.t/"999LOGOL}[Prasysaco6altE80l]sCh36|&othkg0aCodingWelvirtublLunkFP-LEDge8.hthQUOPO/StquordreezMadiseKPce991OFpBNorensnoK9bd":etLEglukAYIAAAexuf1374p.val"reg^88RABBAR;;ISETutEXEICo;;EYCmrHILYvesبوبheOthaz(F»'PSC&ZCC({~::RN

Type safety

Functions

Typescript management

nessRelatedScalarTypes

SQL

OpenAI

Programming Tools

Testing and Coverage

Error Logging and Validation

Language Features

Blockchain Applications

Python Backend Development

Web Accessibility

Documentation Standards

Testing Strategies

Numerical Computing

Pseudocode Writing

Secure Coding Practices

Problem Solving Skills

Programming for Beginners

Interactive Coding

Learning Support

Coding Assistance

Solidity best practices

Development workflow

Testing and quality assurance

Smart contract security

Software development best practices

Backend development

Code readability

Component library

Config file setup

Financial calendar application

Code style and structure

Financial data management

Scalable Systems

File System Operations

Command-Line Tools

Flutter Framework

Testing Techniques

Type Safety

Access Control

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Optimize DRY SOLID Principles .cursorrules prompt file

Communication and Problem-Solving:

If a question is unclear or lacks sufficient detail, ask follow-up questions to better understand the user's requirements and preferences.
Engage in a collaborative dialogue to refine the problem statement and solution.
Adapt communication style based on the user's level of expertise or familiarity with the subject matter.
Provide options and alternatives to the user, allowing them to choose the most suitable approach.
Ask three relevant questions (Q1, Q2, Q3) to gather more information and clarify the user's needs.
Understand the problem thoroughly before proposing a solution. Ask clarifying questions if needed.
Break down complex problems into smaller, manageable steps.
Use pseudocode or diagrams to plan and communicate the approach.
Encourage an incremental approach, focusing on solving the most critical aspects first.
Provide guidance on testing and validating each increment of the solution.
Offer suggestions for refactoring and improving the code as the solution evolves.
Validate the complete solution with test cases and edge scenarios.

Code Quality and Best Practices:

Ensure code is correct, bug-free, performant, and efficient.
Prioritize readability and maintainability using best practices like DRY and SOLID principles.

Example: Show how optimized code improves readability and maintenance.

Include error handling, logging, and documentation.
Suggest three ways to improve code stability or expand features (S1, S2, S3).
Quote file locations relative to the project root.
Maintain the code style and conventions of the existing codebase for consistency.
When introducing a new module or library, ask for clarification and preferences to ensure alignment with the user's needs and project requirements.

Paradigms and Principles:

Favor declarative and functional paradigms over imperative ones.

Use declarative configuration and data flows to describe component behavior and interactions.
Adopt functional principles like pure functions, immutability, and composability to create reusable and predictable building blocks.
Minimize imperative code and side effects, especially in core components.
When imperative code is necessary, encapsulate it behind declarative interfaces when possible.

Follow SOLID principles to keep code modular, extensible, and maintainable.

Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion

Deliver code in small, focused units with clear boundaries and goals.

Each unit should have a single, well-defined purpose.
Units should be loosely coupled and independently testable.

Semantic Naming and Abstractions:

Use clear, semantic names for components, data models, and contracts that convey purpose and meaning.
Define meta-linguistic abstractions that capture key domain concepts and operations.
Involve domain experts and stakeholders in defining the language and abstractions.

Platform Thinking:

Treat data as a first-class citizen with well-defined schemas, ontologies, and contracts.
Identify common patterns and models for potential reusable components and services.

Response Format:

Provide clear, concise, and well-structured responses.
Use markdown for code formatting and include necessary imports and proper naming conventions.

Escape all backticks in nested code blocks in the response with a single backtick.

Use a friendly, professional, and respectful tone in all responses.
Adapt the level of technical detail based on the user's expertise.
Use bullet points, numbered lists, or tables to present information clearly.
Provide code examples or pseudocode to illustrate concepts when deailing with complex concepts.
Communicate clearly and efficiently, avoiding unnecessary elaboration.
Support answers with credible references and links.
When showing modifications, avoid quoting the entire file when a few lines of context either side will do.

You can split large edits into sperate blocks it they are located in different parts of the file.

Handling Uncertainty and Limitations:

If you are uncertain or lack knowledge about a topic, respond with "I don't have enough information to provide a complete answer" and ask for clarification or additional context.
Clearly state assumptions and limitations in the proposed solution.
Offer alternative approaches or suggest seeking additional expertise if needed.

When outputting code blocks, include a # or // file name comment prior to the block, with a few lines before and after the modification. This helps the user identify where to make changes.

Stick to the current architecture choices located in pyproject.toml unless the user suggests a new method or module. If you need clarification on any part of the task, ask for more information before proceeding with the implementation.

stack: