nextjs-react-redux-typescript-cursor-rules
Comprehensive Next.js, React, Redux, and TypeScript development guidelines covering SOLID principles, component architecture, and best practices.
What this skill does
# Next.js React Redux TypeScript Cursor Rules Complete development guidelines for building maintainable, scalable applications with Next.js, React, Redux Toolkit, and TypeScript. ## Development Philosophy - Produce maintainable, scalable code following SOLID principles - Favor functional and declarative approaches over imperative styles - Prioritize type safety and static analysis - Embrace component-driven architecture ## Code Style Standards - **Indentation**: Use tabs - **Strings**: Use single quotes (unless escaping needed) - **Semicolons**: Omit unless disambiguation required - **Operators**: Space around infix operators - **Functions**: Space before declaration parentheses - **Equality**: Always use `===` over `==` - **Line length**: Maximum 80 characters - **Conditionals**: Use braces for multi-line if statements - **Collections**: Trailing commas in multiline arrays/objects ## Naming Conventions | Convention | Usage | |------------|-------| | PascalCase | Components, type definitions, interfaces | | kebab-case | Directory and file names (e.g., `user-profile.tsx`) | | camelCase | Variables, functions, methods, hooks, properties, props | | UPPERCASE | Environment variables, constants, global configurations | ### Prefixes - **Event handlers**: `handle` (e.g., `handleClick`) - **Booleans**: verbs (e.g., `isLoading`, `hasError`, `canSubmit`) - **Custom hooks**: `use` (e.g., `useAuth`, `useForm`) ## React Best Practices ### Components - Use functional components with TypeScript interfaces - Define components using `function` keyword - Extract reusable logic into custom hooks - Apply composition patterns properly - Leverage `React.memo()` strategically - Implement cleanup in `useEffect` hooks ### Performance - Use `useCallback` for memoizing functions - Apply `useMemo` for expensive computations - Avoid inline function definitions in JSX - Implement code splitting via dynamic imports - Use proper `key` props in lists (never use index) ## Next.js Best Practices ### Core - Use App Router for routing - Implement metadata management - Apply proper caching strategies - Implement error boundaries ### Components - Use built-in components: `Image`, `Link`, `Script`, `Head` - Implement loading states - Use appropriate data fetching methods ### Server Components - Default to Server Components - Use URL query parameters for server state - Apply `use client` only when necessary: - Event listeners - Browser APIs - State management - Client libraries ## TypeScript Implementation - Enable strict mode - Define clear interfaces for props, state, and Redux structure - Use type guards for undefined/null safety - Apply generics for flexibility - Leverage utility types (`Partial`, `Pick`, `Omit`) - Prefer `interface` over `type` for objects - Use mapped types for dynamic type variations ## UI and Styling ### Libraries - **Shadcn UI**: Consistent, accessible components - **Radix UI**: Customizable primitives - **Composition patterns**: Modularity ### Styling - Tailwind CSS utility-first approach - Mobile-first responsive design - Dark mode via CSS variables or Tailwind's dark mode - Accessible color contrast ratios - Consistent spacing values - CSS variables for theme colors ## State Management ### Local State - `useState` for component-level state - `useReducer` for complex state - `useContext` for shared state ### Global State (Redux Toolkit) - Use `createSlice` for combined state/reducers/actions - Normalize state structure - Use selectors for access encapsulation - Separate concerns by feature (avoid monolithic slices) ## Error Handling and Validation ### Forms - Zod for schema validation - React Hook Form integration - Clear error messaging ### Error Boundaries - Catch and handle React tree errors gracefully - Log errors to external services (e.g., Sentry) - Display user-friendly fallback UIs ## Testing ### Unit Testing - Jest and React Testing Library - Arrange-Act-Assert pattern - Mock external dependencies and API calls ### Integration Testing - Focus on user workflows - Proper test environment setup/teardown - Selective snapshot testing - Use testing utilities (`screen` in RTL) ## Accessibility (a11y) - Semantic HTML - Accurate ARIA attributes - Full keyboard navigation - Proper focus management - Accessible color contrast - Logical heading hierarchy - Accessible interactive elements - Clear error feedback ## Security - Input sanitization to prevent XSS - DOMPurify for HTML sanitization - Proper authentication methods ## Internationalization (i18n) - next-i18next for translations - Locale detection - Number and date formatting - RTL support - Currency formatting ## Documentation - JSDoc for all public functions, classes, methods, interfaces - Complete sentences with proper punctuation - Clear, concise descriptions - Proper markdown, code blocks, links, headings, lists - Examples when appropriate
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.