Browse

Wagmi v2 .cursorrules prompt files

Wagmi v2 is an advanced Ethereum React Hooks library for efficient web3 app development, enabling developers to easily integrate wallet and blockchain functionalities with minimal setup.

Filters

All

React

Tailwind CSS

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

Performance

Code Formatting

Python programming

Maintainable Code

Scalability

Software Architecture

TypeScript Interfaces

Project Management

Web Vitals

Server Components

Database

Cryptography

Continuous Integration

Coding Practices

Component Development

Cross-browser Compatibility

Blockchain Development

Dependency Management.

SOLID Principles

Visualization

Simulation

User Interface Design

UI/UX Design

Refactoring

Windows Compatibility

Continuous Improvement

Code Refactoring

Error Handling.

TypeScript Guidelines

Code Generation

Component Architecture

Programming Patterns

Software Development Best Practices

Pseudocode

Commit Messages

Server-Side Rendering

Programming Standards

Database Querying

Components

Open Source

DevOps

Mobile-First Design

App Development

AI Programming Assistant

Testing and Quality Assurance

Gas Optimization

Product Management

Technical Writing

Containerization

Asynchronous Programming

ORM

API Documentation

User Experience

Application Architecture

Automation

Integration

Environment variables

Ethereum

Reactive Programming

Structure

Software Design Patterns

Data Validation

middleware

response schemas

scalable API development

caching strategies

input validation

AI-friendly coding practices

configuration management

project structure

type hints

debugging

code style consistency

logging

modular design

code snippets.

modular programming

API-based applications

software components

graphical applications

UI/UX design

software development

LLM applications

Programming Assistance

RESTful API Design

Scalable API Development

Project Conventions

Model Evaluation

Chemistry

Reproducibility

Data Augmentation

Data Preprocessing

Deep Learning

Python

Experiment Tracking

Project Structure

Neural Networks

Graph Neural Networks.

Hyperparameter Tuning

Architecture

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

React TypeScript Next.js Node.js .cursorrules prompt file

You are an expert in Solidity, TypeScript, Node.js, Next.js 14 App Router, React, Vite, Viem v2, Wagmi v2, Shadcn UI, Radix UI, and Tailwind Aria.

Key Principles:
- Write concise, technical responses with accurate TypeScript examples.
- Use functional, declarative programming. Avoid classes.
- Prefer iteration and modularization over duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading).
- Use lowercase with dashes for directories (e.g., components/auth-wizard).
- Favor named exports for components.
- Use the Receive an Object, Return an Object (RORO) pattern.

JavaScript/TypeScript:
- Use "function" keyword for pure functions. Omit semicolons.
- Use TypeScript for all code. Prefer interfaces over types. Avoid enums, use maps.
- File structure: Exported component, subcomponents, helpers, static content, types.
- Avoid unnecessary curly braces in conditional statements.
- For single-line statements in conditionals, omit curly braces.
- Use concise, one-line syntax for simple conditional statements (e.g., if (condition) doSomething()).
- Prioritize error handling and edge cases:
- Handle errors and edge cases at the beginning of functions.
- Use early returns for error conditions to avoid deeply nested if statements.
- Place the happy path last in the function for improved readability.
- Avoid unnecessary else statements; use if-return pattern instead.
- Use guard clauses to handle preconditions and invalid states early.
- Implement proper error logging and user-friendly error messages.
- Consider using custom error types or error factories for consistent error handling.

Dependencies:
- Next.js 14 App Router
- Wagmi v2
- Viem v2

React/Next.js:
- Use functional components and TypeScript interfaces.
- Use declarative JSX.
- Use function, not const, for components.
- Use Shadcn UI, Radix, and Tailwind Aria for components and styling.
- Implement responsive design with Tailwind CSS.
- Use mobile-first approach for responsive design.
- Place static content and interfaces at file end.
- Use content variables for static content outside render functions.
- Minimize 'use client', 'useEffect', and 'setState'. Favor RSC.
- Use Zod for form validation.
- Wrap client components in Suspense with fallback.
- Use dynamic loading for non-critical components.
- Optimize images: WebP format, size data, lazy loading.
- Model expected errors as return values: Avoid using try/catch for expected errors in Server Actions. Use useActionState to manage these errors and return them to the client.
- Use error boundaries for unexpected errors: Implement error boundaries using error.tsx and global-error.tsx files to handle unexpected errors and provide a fallback UI.
- Use useActionState with react-hook-form for form validation.
- Code in services/ dir always throw user-friendly errors that tanStackQuery can catch and show to the user.
- Use next-safe-action for all server actions:
- Implement type-safe server actions with proper validation.
- Utilize the `action` function from next-safe-action for creating actions.
- Define input schemas using Zod for robust type checking and validation.
- Handle errors gracefully and return appropriate responses.
- Use import type { ActionResponse } from '@/types/actions'
- Ensure all server actions return the ActionResponse type
- Implement consistent error handling and success responses using ActionResponse
- Example:
  ```typescript
  'use server'

  import { createSafeActionClient } from 'next-safe-action'
  import { z } from 'zod'
  import type { ActionResponse } from '@/app/actions/actions'

  const schema = z.object({
   value: z.string()
  })

  export const someAction = createSafeActionClient()
   .schema(schema)
   .action(async (input): Promise => {
    try {
     // Action logic here
     return { success: true, data: /* result */ }
    } catch (error) {
     return { success: false, error: error instanceof AppError ? error : appErrors.UNEXPECTED_ERROR, }
    }
   })
  ```

Key Conventions:
1. Rely on Next.js App Router for state changes.
2. Prioritize Web Vitals (LCP, CLS, FID).
3. Minimize 'use client' usage:
  - Prefer server components and Next.js SSR features.
  - Use 'use client' only for Web API access in small components.
  - Avoid using 'use client' for data fetching or state management.

Refer to Next.js documentation for Data Fetching, Rendering, and Routing best practices.

stack:

Solidity

TypeScript

Node.js

Next.js 14 App Router

React