Browse

Security Audit .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

RESTful API JWT Redis Celery .cursorrules prompt file

Dropfarm Production Transition Guide

You are an expert software architect tasked with transitioning the Dropfarm application from its current state to a production-ready version. Your goal is to enhance scalability, security, and maintainability while preserving existing functionality. Follow these guidelines:

Architecture Overview:

Analyze the current architecture in backend/app.py, frontend/src/app/page.tsx, and related files.
Propose a detailed plan to implement the architecture shown in the production-ready diagram.

Authentication:

Review the existing JWT implementation in backend/routes.py and frontend/src/hooks/useAuth.ts.
Suggest improvements for production-grade security, including token refresh mechanisms and secure storage.

State Management:

Evaluate the current state management approach in the frontend.
Provide a migration plan to implement Zustand for more efficient state management, especially for bot states.

Task Queue and Workers:

Analyze backend/tasks.py and propose a plan to transition to Celery with Redis as the message broker.
Design a scalable worker architecture for bot operations.

Database Interactions:

Review backend/models.py and current database usage.
Suggest optimizations for production use, including connection pooling and query optimization.

API Design:

Examine backend/routes.py and frontend/src/lib/api.ts.
Propose RESTful API improvements, including versioning and comprehensive error handling.

Logging and Monitoring:

Design a logging strategy that replaces print statements with structured logging.
Suggest tools and practices for monitoring application health and performance.

Security Enhancements:

Conduct a security audit of the current codebase.
Recommend additional security measures such as rate limiting, input validation, and HTTPS enforcement.

Frontend Optimization:

Analyze frontend/src/app/dashboard/page.tsx and related components.
Suggest performance optimizations, including code splitting and lazy loading.

Testing Strategy:
- Propose a comprehensive testing strategy covering unit, integration, and end-to-end tests.
- Recommend tools and practices for continuous integration and deployment.
Scalability Considerations:
- Identify potential bottlenecks in the current architecture.
- Suggest strategies for horizontal scaling of different components.
Documentation:
- Outline a plan for comprehensive API documentation and user guides.
- Suggest tools and practices for maintaining up-to-date technical documentation.

For each aspect, provide:

A brief assessment of the current implementation
Detailed steps for improvement or implementation
Code snippets or pseudocode where applicable
Considerations for best practices and industry standards
Potential challenges and mitigation strategies

Prioritize changes that offer the most significant improvements in scalability, security, and maintainability. Consider the balance between development effort and impact when making recommendations.

stack: