AI SummaryHyperstaker-ui Cursor Rules is a comprehensive set of development guidelines for building the Hyperstaker platform, enforcing standards across TypeScript, Next.js 14, React 18, and Web3 libraries (Wagmi, Viem) to ensure consistent, performant code.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "hyperstaker-ui — Cursor Rules" prompt rules to my project. Repository: https://github.com/Hyperstaker/hyperstaker-ui Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Hyperstaker is a decentralized platform that catalyzes early-stage software projects by linking early contributors to potential project successes. It bridges the funding gap by generating utility and demand for Hypercerts, allowing users to forecast and invest in promising public goods projects.
Vercel Build Requirements
• Ensure all code follows Next.js best practices • Follow strict ESLint rules for Vercel deployment • Verify import/export syntax compatibility • Check for proper TypeScript types • Avoid common Vercel build pitfalls
General AI Behavior
description: "Base rules for AI interactions across the project" pattern: "*/" rules: # ESLint Rules • Follow ESLint v8.56.0 configuration • Use Unix line endings (LF) • Follow consistent quote style • Handle unused variables with warnings or _ prefix • No React import required • No PropTypes required (use TypeScript) • TypeScript explicit return types optional • Always use double quotes " not single quotes ' # TypeScript Standards • Use TypeScript for all new code • Prefer interfaces over types • Implement proper type definitions • Avoid type assertions unless necessary • Use proper generic constraints • Follow strict TypeScript checking # Next.js Standards • Follow Next.js 14 App Router patterns • Use server components by default • Implement proper error boundaries • Handle client/server code separation • Follow Server Component best practices # React Standards • Use functional components • Use TypeScript interfaces for props • Follow React 18 best practices • Minimize client-side state • Use Server Components where possible # Code Style • Use 2 spaces for indentation • Use meaningful variable names • Group related code blocks • Keep functions small and focused • Use declarative JSX # Project Structure • Use lowercase with dashes for directories • Follow Next.js 14 app directory structure • Organize components logically • Keep related files together # Library Usage • Use Wagmi v2 hooks (no v1 patterns) • Use Viem v2 API • Follow Mantine v7 patterns • Use React Hook Form v7 • Use Prisma v6.4.1 client methods # Performance • Minimize 'use client' directives • Use React Suspense boundaries • Implement proper loading states • Follow image optimization best practices • Use dynamic imports for large components # Documentation • Add JSDoc comments for public functions • Include example usage where appropriate • Document complex logic • Maintain clear component interfaces # Version Requirements • Next.js: v14.1.0 • React: v18 • TypeScript: v5 • Node.js: Latest LTS • ESLint: v8.56.0
Code Quality
• Follow language-specific best practices • Maintain consistent indentation (2 spaces) • Use meaningful variable and function names • Group related code blocks logically
Next.js Specific
• Use App Router patterns correctly • Implement proper error boundaries • Follow Server Component best practices • Handle client/server code separation properly
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts