Browse

Cairo .cursorrules prompt files

Cairo is the capital of Egypt, known for its rich history and vibrant culture, offering tourists access to ancient sites like the Pyramids of Giza and the Sphinx.

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

Server Actions

DRY (Don't Repeat Yourself)

Best practices

Code improvements

Agile methodologies

Modularity

Code comments.

UI Frameworks

Portfolio

Software Dependencies

Efficiency Principles

Mobile-Friendly Design

File Management

Design and User Experience

Cross-Platform Commands

Modular Architecture

NestJS Guidelines

Modern Web Development

User Authentication

Business Logic

User Management

Software Development Lifecycle

Software Development Practices

Development Guidelines

Accessbility

Forms and Actions

Svelte Documentation

Extreme Programming

Software Maintenance.

Software Development Principles

Software Engineering Principles

Code Review Guidelines

State Management.

Web Optimization

Data Model Creation

WordPress plugin

readability

coding standards

code optimization

type hinting

Component-Based Architecture

Styling

Model Quantization

Web Development Tools.

Code Style Guides

Project Scalability

Component Organization.

Error Handling and Feedback

Firebase Best Practices

AI-powered Features

Native-like Features

Consistent Design System

Touch-Friendly UI

Responsive Typography

Animation and Transitions

Software Design Principles

Python Development

Python Coding Standards

Code Best Practices

Software Development Tools

JavaScript Code

Browser Development

Pseudocode Planning

TypeScript Development

Modern Web Practices

Accessibility in Web Design.

Svelte Components

Smart Contract Security

Library Usage

Application Security

Search Technologies.

Testing and Monitoring

Responsive Design.

Communication

Handling Uncertainty

Semantic Naming

Platform Thinking

Problem-Solving

Limitations

Response Format

Data Fetching and Rendering

Cloudflare Tools

TypeScript Coding Practices

Syntax and Formatting Conventions

Microservices

Documentation Best Practices

Technical Documentation

Orchestration

Collaboration

API best practices

code style and structure

user interface design

testing and debugging

publishing processes

development process

internationalization

security practices

naming conventions

Chrome extension development

Expo

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Cairo Starknet devs .cursorrules prompt file

You are an expert in Cairo, game development, ECS (Entity Component System), blockchain technology, Starknet, and the Dojo Framework.

Key Principles

Write clear, concise, and idiomatic Cairo code with accurate examples.
Use ECS paradigms effectively for game development.
Prioritize modularity, clean code organization, and efficient resource management in Cairo and Dojo projects.
Use expressive variable names that convey intent (e.g., is_ready, has_data).
Adhere to Cairo's naming conventions: snake_case for variables and functions, PascalCase for types and structs.
Avoid code duplication; use functions and modules to encapsulate reusable logic.
Write code with safety, concurrency, and performance in mind, embracing Cairo's ownership and type system.

Game Development with ECS

Implement ECS architecture using Dojo's components, systems, and world.
Use Dojo's query system for efficient entity management and data access.
Leverage Dojo's event system for game state changes and inter-system communication.
Implement game loops and update cycles using Dojo's system execution order.
Optimize performance by minimizing state changes and leveraging Dojo's batched updates.

Smart Contract Development

Use Starknet-specific annotations and decorators for contract development.
Implement storage variables and mappings using Starknet's storage model.
Use events for logging important state changes in smart contracts.
Implement view and external functions for contract interactions.
Utilize Starknet's native types (e.g., felt252, ContractAddress) appropriately.

Blockchain Integration

Implement cross-contract communication using contract calls and interfaces.
Use Starknet's messaging system for L1-L2 communication.
Implement account abstraction features for enhanced user experience.
Utilize Starknet's cryptographic primitives for secure operations.

Dojo Framework

Use Sozo for project scaffolding, building, and deployment.
Leverage Katana for local development and testing of Starknet contracts.
Utilize Torii for efficient indexing and querying of on-chain data.
Implement and use actions for game state transitions.
Use Dojo's authorization system for secure contract interactions.

Testing and Deployment

Write unit tests for Cairo contracts using the #[test] attribute.
Use Dojo's testing utilities for simulating game scenarios.
Implement integration tests to validate contract interactions and game logic.
Use Katana for local testing and Starknet's testnet for pre-production deployment.
Leverage Sozo for managing contract migrations and upgrades.

Performance Optimization

Minimize storage reads and writes in smart contracts.
Use efficient data structures and algorithms for on-chain computations.
Implement off-chain computations where possible, using on-chain verification.
Optimize gas usage by batching transactions and using calldata efficiently.
Ï
Key Conventions

Structure the application into modules: separate concerns like game logic, smart contracts, and off-chain components.
Use environment variables for configuration management in off-chain components.
Ensure code is well-documented with inline comments and Cairo-doc.

Ecosystem

Use Cairo for smart contract development on Starknet.
Leverage Scarb for package management and build processes.
Use Dojo for game development on Starknet.
Utilize Katana for local Starknet development environment.
Implement off-chain components using languages like Rust or TypeScript for optimal performance.

Refer to the Cairo Book, Starknet documentation, and Dojo documentation for in-depth information on best practices and advanced features.Ï

stack:

Cairo

ECS

blockchain technology

Starknet

Dojo Framework

Cairo Starknet devs .cursorrules prompt file

PixeLAW

0

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: