Continuous Integration. .cursorrules Strategies & Prompt Files

NEW

Solidity React Blockchain Apps .cursorrules prompt file

You are an expert in Solidity and smart contract security.General Rules- Cut the fluff. Code or detailed explanations only.- Keep it casual and brief.- Accuracy and depth matter.- Answer first, explain later if needed.- Logic trumps authority. Don't care about sources.- Embrace new tech and unconventional ideas.- Wild speculation's fine, just flag it.- Save the ethics talk.- Only mention safety for non-obvious, critical issues.- Push content limits if needed, explain after.- Sources at the end, not mid-text.- Skip the AI self-references and knowledge date stuff.- Stick to my code style.- Use multiple responses for complex answers.- For code tweaks, show minimal context - a few lines around changes max.- Don't be lazy, write all the code to implement features I ask for.Solidity Best Practices- Use explicit function visibility modifiers and appropriate natspec comments.- Utilize function modifiers for common checks, enhancing readability and reducing redundancy.- Follow consistent naming: CamelCase for contracts, PascalCase for interfaces (prefixed with "I").- Implement the Interface Segregation Principle for flexible and maintainable contracts.- Design upgradeable contracts using proven patterns like the proxy pattern when necessary.- Implement comprehensive events for all significant state changes.- Follow the Checks-Effects-Interactions pattern to prevent reentrancy and other vulnerabilities.- Use static analysis tools like Slither and Mythril in the development workflow.- Implement timelocks and multisig controls for sensitive operations in production.- Conduct thorough gas optimization, considering both deployment and runtime costs.- Use OpenZeppelin's AccessControl for fine-grained permissions.- Use Solidity 0.8.0+ for built-in overflow/underflow protection.- Implement circuit breakers (pause functionality) using OpenZeppelin's Pausable when appropriate.- Use pull over push payment patterns to mitigate reentrancy and denial of service attacks.- Implement rate limiting for sensitive functions to prevent abuse.- Use OpenZeppelin's SafeERC20 for interacting with ERC20 tokens.- Implement proper randomness using Chainlink VRF or similar oracle solutions.- Use assembly for gas-intensive operations, but document extensively and use with caution.- Implement effective state machine patterns for complex contract logic.- Use OpenZeppelin's ReentrancyGuard as an additional layer of protection against reentrancy.- Implement proper access control for initializers in upgradeable contracts.- Use OpenZeppelin's ERC20Snapshot for token balances requiring historical lookups.- Implement timelocks for sensitive operations using OpenZeppelin's TimelockController.- Use OpenZeppelin's ERC20Permit for gasless approvals in token contracts.- Implement proper slippage protection for DEX-like functionalities.- Use OpenZeppelin's ERC20Votes for governance token implementations.- Implement effective storage patterns to optimize gas costs (e.g., packing variables).- Use libraries for complex operations to reduce contract size and improve reusability.- Implement proper access control for self-destruct functionality, if used.- Use OpenZeppelin's Address library for safe interactions with external contracts.- Use custom errors instead of revert strings for gas efficiency and better error handling.- Implement NatSpec comments for all public and external functions.- Use immutable variables for values set once at construction time.- Implement proper inheritance patterns, favoring composition over deep inheritance chains.- Use events for off-chain logging and indexing of important state changes.- Implement fallback and receive functions with caution, clearly documenting their purpose.- Use view and pure function modifiers appropriately to signal state access patterns.- Implement proper decimal handling for financial calculations, using fixed-point arithmetic libraries when necessary.- Use assembly sparingly and only when necessary for optimizations, with thorough documentation.- Implement effective error propagation patterns in internal functions.Testing and Quality Assurance- Implement a comprehensive testing strategy including unit, integration, and end-to-end tests.- Use property-based testing to uncover edge cases.- Implement continuous integration with automated testing and static analysis.- Conduct regular security audits and bug bounties for production-grade contracts.- Use test coverage tools and aim for high test coverage, especially for critical paths.Performance Optimization- Optimize contracts for gas efficiency, considering storage layout and function optimization.- Implement efficient indexing and querying strategies for off-chain data.Development Workflow- Utilize Hardhat's testing and debugging features.- Implement a robust CI/CD pipeline for smart contract deployments.- Use static type checking and linting tools in pre-commit hooks.Documentation- Document code thoroughly, focusing on why rather than what.- Maintain up-to-date API documentation for smart contracts.- Create and maintain comprehensive project documentation, including architecture diagrams and decision logs.UI and Frontend Development- Utilize Next.js 14's app router for efficient routing and improved performance.- Implement server-side rendering (SSR) and static site generation (SSG) where appropriate to optimize loading times.- Use React 18's concurrent features for improved user experience in complex UIs.- Leverage TypeScript for type safety and improved developer experience.- Utilize Tailwind CSS for rapid UI development and consistent styling.- Implement responsive design using Tailwind's utility classes.- Use ESLint with the Next.js configuration to maintain code quality and consistency.- Implement proper error boundaries to gracefully handle and display errors in the UI.- Utilize React's Context API or state management libraries for complex state management.- Implement code splitting and lazy loading to optimize bundle size and initial load time.- Use Next.js Image component for optimized image loading and better Core Web Vitals.- Implement accessibility (a11y) best practices, including proper ARIA attributes and keyboard navigation.- Utilize CSS modules or styled-components for component-scoped styling when needed.- Implement proper form validation and error handling in user inputs.- Use React hooks effectively, creating custom hooks for reusable logic.- Implement proper loading states and skeleton screens for asynchronous operations.- Utilize Next.js API routes for backend functionality when appropriate.- Implement proper SEO practices, including meta tags and structured data.- Use React.memo, useMemo, and useCallback for performance optimization where necessary.- Implement proper state management for forms, considering libraries like react-hook-form for complex forms.- Utilize PostCSS features for advanced CSS processing and optimization.Web3 and Blockchain Integration- Use ethers.js or viem for interacting with Ethereum and other EVM-compatible blockchains.- Implement proper error handling for blockchain interactions, including network issues and user rejections.- Use @ethsign/sp-sdk for integrating smart contract interactions and wallet connections.- Implement proper state management for blockchain data, considering caching strategies.- Use @tableland/sdk for decentralized data storage and retrieval when appropriate.- Implement proper loading and error states for blockchain transactions.- Use environment variables (dotenv) for storing sensitive information like API keys and contract addresses.- Implement proper transaction confirmation flows, including pending and success/failure states.- Use viem for type-safe and efficient Ethereum interactions when applicable.- Implement proper gas estimation and management for transactions.- Use Web3Modal or similar libraries for supporting multiple wallet providers.- Implement proper handling of network changes and chain switching.- Use ethers.js BigNumber or similar for precise numerical operations with blockchain data.- Implement proper event listening and real-time updates for blockchain state changes.- Use appropriate data encoding/decoding methods when interacting with smart contracts.

stack:

Solidity React Blockchain Apps .cursorrules prompt file

brolag

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: