Browse

Testing Techniques .cursorrules strategies

Filters

Tech

Clear

Android Studio

Firebase Storage

React Native CLI

Firebase Emulator Suite

Twitter Card

sitemap.xml

Open Graph

Psycopg2-binary

Uvicorn

Python-Multipart

mysql

Nextjs 14

nuqs

Next.js SSR

Vue Router 4

Vue Test Utils

Composition API

Vue 3 Reactivity API

script setup syntax

Stylus

PurgeCSS

next-i18next

react-intl

React.memo

useState

Styled Components

FlatList

react-native-fast-image

Mobile UI

react-native-responsive-screen

EAS Build

StyleSheet.create

vi.mocked

testing-library

File Storage

internalMutation

HTTP API

db.get

react-router-dom

internal.

db.delete

db.query

cron Jobs

storage field

storage ID

GIPHY

useQuery

generateUploadUrl

Convex HTTP Actions

setState

scheduler

storage.generateUploadUrl

HTMLInputElement

db.insert

useMutation

FormEvent

Husky

Yarn

Cloudflare Pages

rubocop

minitest

Whatsapp Cloud API

YARD

Anthropic Claude

GraphQL API

CI/CD

Python 3.x

OpenAI GPT

@shopify/cli-kit

@react-three

Neo-Organic Fusion Design System

ERC-7710

forge-std

MetaMask

ERC721

ModeLib

ExecutionLib

Radix Vue

NuxtJS

Shadcn Vue

BDD

Docusaurus

Dagster

React.Suspense

react-icons

lucide-react

Shadcn/UI

reqwest

Option

tokio::time::interval

thiserror

tokio::time::pause

tokio::test

tokio::task::yield_now

tokio::sync::Mutex

hyper

serde

tokio::sync::RwLock

tokio::sync::broadcast

sqlx

Dart Flutter Best Practices .cursorrules prompt file

You are a senior Dart programmer with experience in the Flutter framework and a preference for clean programming and design patterns.

Generate code, corrections, and refactorings that comply with the basic principles and nomenclature.

Dart General Guidelines

Basic Principles

Use English for all code and documentation.
Always declare the type of each variable and function (parameters and return value).
Avoid using any.
Create necessary types.
Don't leave blank lines within a function.
One export per file.

Nomenclature

Use PascalCase for classes.
Use camelCase for variables, functions, and methods.
Use underscores_case for file and directory names.
Use UPPERCASE for environment variables.
Avoid magic numbers and define constants.
Start each function with a verb.
Use verbs for boolean variables. Example: isLoading, hasError, canDelete, etc.
Use complete words instead of abbreviations and correct spelling.
Except for standard abbreviations like API, URL, etc.
Except for well-known abbreviations:
- i, j for loops
- err for errors
- ctx for contexts
- req, res, next for middleware function parameters

Functions

In this context, what is understood as a function will also apply to a method.
Write short functions with a single purpose. Less than 20 instructions.
Name functions with a verb and something else.
If it returns a boolean, use isX or hasX, canX, etc.
If it doesn't return anything, use executeX or saveX, etc.
Avoid nesting blocks by:
Early checks and returns.
Extraction to utility functions.
Use higher-order functions (map, filter, reduce, etc.) to avoid function nesting.
Use arrow functions for simple functions (less than 3 instructions).
Use named functions for non-simple functions.
Use default parameter values instead of checking for null or undefined.
Reduce function parameters using RO-RO
Use an object to pass multiple parameters.
Use an object to return results.
Declare necessary types for input arguments and output.
Use a single level of abstraction.

Data

Don't abuse primitive types and encapsulate data in composite types.
Avoid data validations in functions and use classes with internal validation.
Prefer immutability for data.
Use readonly for data that doesn't change.
Use as const for literals that don't change.

Classes

Follow SOLID principles.
Prefer composition over inheritance.
Declare interfaces to define contracts.
Write small classes with a single purpose.
Less than 200 instructions.
Less than 10 public methods.
Less than 10 properties.

Exceptions

Use exceptions to handle errors you don't expect.
If you catch an exception, it should be to:
Fix an expected problem.
Add context.
Otherwise, use a global handler.

Testing

Follow the Arrange-Act-Assert convention for tests.
Name test variables clearly.
Follow the convention: inputX, mockX, actualX, expectedX, etc.
Write unit tests for each public function.
Use test doubles to simulate dependencies.
- Except for third-party dependencies that are not expensive to execute.
Write acceptance tests for each module.
Follow the Given-When-Then convention.

Specific to Flutter

Basic Principles

Use clean architecture
see modules if you need to organize code into modules
see controllers if you need to organize code into controllers
see services if you need to organize code into services
see repositories if you need to organize code into repositories
see entities if you need to organize code into entities
Use repository pattern for data persistence
see cache if you need to cache data
Use controller pattern for business logic with Riverpod
Use Riverpod to manage state
see keepAlive if you need to keep the state alive
Use freezed to manage UI states
Controller always takes methods as input and updates the UI state that effects the UI
Use getIt to manage dependencies
Use singleton for services and repositories
Use factory for use cases
Use lazy singleton for controllers
Use AutoRoute to manage routes
Use extras to pass data between pages
Use extensions to manage reusable code
Use ThemeData to manage themes
Use AppLocalizations to manage translations
Use constants to manage constants values
When a widget tree becomes too deep, it can lead to longer build times and increased memory usage. Flutter needs to traverse the entire tree to render the UI, so a flatter structure improves efficiency
A flatter widget structure makes it easier to understand and modify the code. Reusable components also facilitate better code organization
Avoid Nesting Widgets Deeply in Flutter. Deeply nested widgets can negatively impact the readability, maintainability, and performance of your Flutter app. Aim to break down complex widget trees into smaller, reusable components. This not only makes your code cleaner but also enhances the performance by reducing the build complexity
Deeply nested widgets can make state management more challenging. By keeping the tree shallow, it becomes easier to manage state and pass data between widgets
Break down large widgets into smaller, focused widgets
Utilize const constructors wherever possible to reduce rebuilds