Browse

Cross-platform Development .cursorrules strategies

Filters

Tech

Clear

RBAC

obsidian

Discord.py

Loguru

VCRPy

Pytest

CliRunner

Pytest-Recording

Clear

web development

QA best practices

code review

security reviews

Database migrations

Electricity system visualization

Open source software

Australian projects

Async programming

Python development guidelines

Scheduler and task runner

.NET Development

Test Driven Development

Automation Testing

Testing Best Practices

Web Testing

Commit Message Conventions

Code Writing Guidelines

Development Best Practices

Dependencies Management

Python Conventions

Database Modeling

Authentication Security

Python Full-Stack Development.

Framework Development

Asynchronous Processing

Svelte

Overview

Scalable Architecture

Development Environment

Deployment Strategy

Digital Transactions

React Native

Event Management

AI Algorithms

Documentation and Best Practices

Real-Time Features

Maintenance and Support

Firebase Integration

Project Setup

Social Features

Internal Linking

Blogging

External Linking

Page Speed

Schema Markup

Core Web Vitals

Mobile Optimization

User Engagement

Content Optimization

URL Structure

Real-time Graphics

Visual Experience Tools

Full-Stack Development

Error Handling and Validation

Code Style and Structure

Front-End Development

Web Development Strategies

Server Side Rendering

Server-side Logic

Code Patterns

Turborepo

Radix UI

Server-side Development

PostgreSQL

Prisma

Shadcn UI

Forms and Validation

Next.js Best Practices

Web Development Guide

Type Checking

JavaScript Best Practices

Testing Guidelines

APIs

Scheduling

Convex

Cron Jobs

HTTP Requests

CSS Frameworks

Exporting Components

File Upload

Error Logging

Module Exportation

Code Formatting and Style

Package Management

Testing and Validation

Workspace Structure

UI Optimization

Performance Testing

Game Mechanics

Terminal Games

Ruby Programming

Software Development Guidelines

Beginner Programming

Programming Education

Code Feedback

Coding Basics

Learning to Code

Problem Solving

AI Workflows

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Next.js Expo Tailwind CSS .cursorrules prompt file

Dishify Project Guidelines

Project Overview

Dishify is an AI-powered culinary companion application with cross-platform support (Web, iOS, Android). It provides instant recipe generation, ingredient lists, and smart shopping features.

Tech Stack

Next.js (14.2.7) for web application
Expo (SDK 51.0.31) for mobile applications
React Native (0.74.2) for cross-platform development
Tailwind CSS (3.4.4) for styling
tRPC (11.0.0) for type-safe API communication
Cloudflare Workers (3.73.0) for serverless backend with Hono
Cloudflare D1 for database
Supabase for authentication
TypeScript (5.5.4) as the primary language

Project Structure

apps/
expo/: Expo mobile app
next/: Next.js web app
packages/
api/: Backend API and database schema
app/: Shared application logic
ui/: Shared UI components
data_utils/: Utility scripts for preparing recipe data for the database

Code Style and Conventions

TypeScript is used for type safety across the project.
A functional programming approach is followed where possible.
Arrow functions are used for component definitions and callbacks.
const is used for variable declarations unless reassignment is necessary.
async/await is used for asynchronous operations.
ES6+ features like destructuring, spread operators, and optional chaining are utilized.

File Naming Conventions

kebab-case is used for file names (e.g., global-error.tsx).
PascalCase is used for component names (e.g., HomeScreen.tsx).
.tsx extension is used for React components and .ts for plain TypeScript files.
index.tsx is used for main component files in a directory.

Styling

Tailwind CSS is used for styling components.
Custom theme is defined in @dishify/ui/src/theme.js.
nativewind is used for React Native styling.

State Management

React Query is used for server state management.
Jotai is used for client-side state management.

API and Data Fetching

tRPC is used for type-safe API communication.
API routes are defined in packages/api/src/routes/.
React Query hooks are used for data fetching and caching.

Error Handling and Logging

Error boundaries are implemented for graceful error handling.
React <Suspense> boundaries are used for handling loading states.
Best practices include:

Catching and handling errors at appropriate levels
Providing user-friendly error messages
Logging errors for debugging purposes

Testing

Unit tests are implemented for critical functions and components.
Jest is used as the testing framework.

Build and Deployment

GitHub Actions are used for CI/CD pipelines.
EAS (Expo Application Services) is used for mobile app builds and submissions.
The web app is deployed to Cloudflare Pages.
The backend is deployed to Cloudflare Workers.

Environment Variables

.env.local is used for local development.
Appropriate prefixes are used for different platforms (e.g., NEXT_PUBLIC_ for Next.js, EXPO_PUBLIC_ for Expo).

Code Quality Tools

Biome is used for linting and formatting.
Biome rules are configured in biome.json.
The linting style enforces consistent code formatting, proper naming conventions, and best practices for React and TypeScript development.

Performance Optimization

React.memo is used for component memoization when necessary.
useCallback() is utilized for optimizing callback functions.
Code splitting and lazy loading are implemented for better performance.

Commenting Style

JSDoc-style comments are used for functions, classes, and interfaces in TypeScript files.
Single-line comments (//) are used for brief explanations or TODO notes.
Multi-line comments (/_ _/) are used for longer explanations or temporary code disabling.
React components are documented with a brief description above the component definition.
Complex logic or algorithms are explained with inline comments.
Comments are kept concise and focus on explaining "why" rather than "what" when the code is not self-explanatory.
For API routes, each endpoint is documented with its purpose, parameters, and return type.

When providing code snippets or recommendations, always include appropriate comments following these guidelines to maintain consistency with the existing codebase.