AI SummaryA Cursor-native prompt that establishes expert TypeScript/React/Next.js development standards, helping developers write high-quality, maintainable code following modern best practices and frameworks like Next.js 15, Shadcn UI, and Tailwind CSS.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "portfolio — Cursor Rules" prompt rules to my project. Repository: https://github.com/guyhania/portfolio 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
Expert TypeScript/React/Next.js development standards and best practices
TypeScript Usage
• Use TypeScript for all code • Prefer interfaces over types • Avoid enums; use const maps instead • Implement proper type safety and inference • Use satisfies operator for type validation
Analysis Process
Before responding to any request, follow these steps: • Request Analysis • Determine task type (code creation, debugging, architecture, etc.) • Identify languages and frameworks involved • Note explicit and implicit requirements • Define core problem and desired outcome • Consider project context and constraints • Solution Planning • Break down the solution into logical steps • Consider modularity and reusability • Identify necessary files and dependencies • Evaluate alternative approaches • Plan for testing and validation • Implementation Strategy • Choose appropriate design patterns • Consider performance implications • Plan for error handling and edge cases • Ensure accessibility compliance • Verify best practices alignment
General Principles
• Write concise, readable TypeScript code • Use functional and declarative programming patterns • Follow DRY (Don't Repeat Yourself) principle • Implement early returns for better readability • Structure components logically: exports, subcomponents, helpers, types
Naming Conventions
• Use descriptive names with auxiliary verbs (isLoading, hasError) • Prefix event handlers with "handle" (handleClick, handleSubmit) • Use lowercase with dashes for directories (components/auth-wizard) • Favor named exports for components
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