Browse

Starknet React .cursorrules prompt files

Starknet React is a library for integrating Starknet blockchain functionality into React applications, enabling seamless access to decentralized network features and smart contract interactions.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

Supabase

CSS

HTML

Next.js App Router

Jest

Docker

PostgreSQL

Redis

TailwindCSS

Tailwind Aria

Pydantic

ESLint

Git

FastAPI

JSDoc

Vercel

Solidity

react-hook-form

pytest

React Testing Library

Zustand

ARIA

Vitest

Suspense

Prettier

Typescript

GitHub Actions

Shadcn

Radix

Celery

dotenv

Prisma

SSR

PEP 8

Expo

Clerk

tRPC

MongoDB

Pinia

Vue.js

JSON

SvelteKit

PHP

SQLAlchemy

Express

VueUse

Drizzle ORM

RESTful API

Laravel

DaisyUI

tanStackQuery

Playwright

SQL

SQLite

GitLab CI

Swagger

JWT

Lighthouse

CORS

Flexbox

Stripe

Drizzle

OpenZeppelin

Markdown

Svelte 5

Astro

Vue Router

styled-components

Nuxt 3

ES6

Elixir

Svelte

GraphQL

Java

Rust

RabbitMQ

GitHub

pandas

scikit-learn

TypeScript

asyncpg

Mongoose

TanStack React Query

None

Turborepo

React Server Components

Clear

Web Development

Frontend Development

Programming

Code Style

Naming Conventions

Testing

State Management

Backend Development

Software Engineering

Code Optimization

Responsive Design

Programming Best Practices

Accessibility

UI Design

Database Management

Version Control

Code Structure

API Development

TypeScript

Authentication

TypeScript Best Practices

Code Quality

Syntax and Formatting

Security

JavaScript

Data Fetching

Best Practices

React

Coding Best Practices

Internationalization

Object-Oriented Programming

API Integration

Coding Standards

Software Development

Performance Optimization

performance optimization

Game Development

SEO

Image Optimization

Testing and Debugging

Code Review

UI and Styling

UI Components

JavaScript Frameworks

User Interface

Clean Code

Deployment

Code Readability

Code Documentation

Modularization

Programming Guidelines

TypeScript Usage

Server-Side Rendering

TypeScript Guidelines

Design Patterns

JavaScript Libraries

UI Development

Error Handling

Web Application Development

Security Best Practices

Code Modularity

Declarative Programming

Full Stack Development

Node.js

API Design

Technical Writing

Testing and Quality Assurance

Coding Guidelines

Code Organization

File Organization

Routing

Static Site Generation

Test-Driven Development

Dependency Injection

Smart Contracts

SEO Optimization

Form Validation

Scalability

Coding Style

functional programming

error handling

Python Libraries

Structure

Semantic HTML

Game Design

Ethereum

React Best Practices

Automation

Vue.js

Next.js

Microservices

Serverless Architecture

Cloud Computing

Form Handling

App Development

Mobile-First Design

DevOps

Styling

Content Management

Clean Code Practices

Show

5

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Tailwind CSS Next.js Guide .cursorrules prompt file

Prompt Generation Rules:
- Analyze the component requirements thoroughly
- Include specific DaisyUI component suggestions
- Specify desired Tailwind CSS classes for styling
- Mention any required TypeScript types or interfaces
- Include instructions for responsive design
- Suggest appropriate Next.js features if applicable
- Specify any necessary state management or hooks
- Include accessibility considerations
- Mention any required icons or assets
- Suggest error handling and loading states
- Include instructions for animations or transitions if needed
- Specify any required API integrations or data fetching
- Mention performance optimization techniques if applicable
- Include instructions for testing the component
- Suggest documentation requirements for the component

General Component Creation Guidelines:
- Prioritize reusability and modularity
- Ensure consistent naming conventions
- Follow React best practices and patterns
- Implement proper prop validation
- Consider internationalization requirements
- Optimize for SEO when applicable
- Ensure compatibility with different browsers and devices

General Rules:
- Enable strict TypeScript (strict: true in tsconfig.json)
- Avoid 'any', prefer 'unknown' with runtime checks
- Explicitly type function inputs and outputs
- Use advanced TypeScript features (type guards, mapped types, conditional types)
- Organize project structure: components, pages, hooks, utils, styles, contracts, services
- Separate concerns: presentational components, business logic, side effects
- Use Biome for code formatting and linting
- Configure Biome as a pre-commit hook

Next.js Rules:
- Use dynamic routes with bracket notation ([id].tsx)
- Validate and sanitize route parameters
- Prefer flat, descriptive routes
- Use getServerSideProps for dynamic data, getStaticProps/getStaticPaths for static
- Implement Incremental Static Regeneration (ISR) where appropriate
- Use next/image for optimized images
- Configure image layout, priority, sizes, and srcSet attributes

TypeScript Rules:
- Enable all strict mode options in tsconfig.json
- Explicitly type all variables, parameters, and return values
- Use utility types, mapped types, and conditional types
- Prefer 'interface' for extendable object shapes
- Use 'type' for unions, intersections, and primitive compositions
- Document complex types with JSDoc
- Avoid ambiguous union types, use discriminated unions when necessary

TailwindCSS and DaisyUI Rules:
- Use TailwindCSS utility classes for styling
- Avoid custom CSS unless absolutely necessary
- Maintain consistent order of utility classes
- Use Tailwind's responsive variants for adaptive designs
- Leverage DaisyUI components for rapid development
- Customize DaisyUI components only when necessary
- Define and use design tokens in tailwind.config.js

Starknet React Rules:
- Centralize blockchain connection management
- Implement automatic reconnection and error handling
- Use React hooks for transaction status management
- Provide clear UI feedback for blockchain interactions
- Implement comprehensive error handling for blockchain operations

Cairo Rules:
- Design modular and maintainable contract structures
- Optimize for gas efficiency
- Minimize state changes and storage access
- Document all contracts and functions thoroughly
- Explain complex logic and implementation choices

Development Process:
- Conduct thorough code reviews via Pull Requests
- Include clear PR descriptions with context and screenshots
- Implement comprehensive automated testing (unit, integration, e2e)
- Prioritize meaningful tests over high coverage numbers
- Use Conventional Commits for commit messages (feat:, fix:, docs:, chore:)
- Make small, incremental commits for easier review and debugging

Biome Rules:
- Use Biome for code formatting and linting
- Configure Biome as a pre-commit hook
- Follow Biome's recommended rules
- Customize Biome configuration in biome.json as needed
- Ensure consistent code style across the project
- Run Biome checks before committing changes
- Address all Biome warnings and errors promptly
- Use Biome's organize imports feature to maintain clean import statements
- Leverage Biome's advanced linting capabilities for TypeScript
- Integrate Biome into the CI/CD pipeline for automated checks
- Keep Biome updated to the latest stable version
- Use Biome's ignore patterns to exclude specific files or directories when necessary

stack: