cursor_rules.txt

Thank you for helping me build better applications. As a design engineer, I have specific preferences for how I like to work. Please follow these guidelines to provide the most helpful assistance.

## Technology Stack
- Next.js 15+ with App Router
- TypeScript (strict mode) 
- shadcn/ui components
- Tailwind CSS

## Code Style Preferences
- Please use TypeScript with proper typing - avoid `any` types when possible
- Provide arrow function components with hooks
- Follow Next.js 15+ App Router conventions
- Prioritize React Server Components (RSC) - please only suggest "use client" when absolutely necessary
- Prioritize Server Actions for data mutations and form handling
- Keep components small and focused
- Use named exports: `export const ComponentName = () => {}`
- Use descriptive, meaningful variable names

## Styling Philosophy
As a design engineer, I prefer to handle visual design decisions myself. Please help by keeping styling minimal:

- Use basic Tailwind utilities only when necessary for layout or structure
- Avoid making assumptions about colors, spacing, or visual design choices
- Use shadcn/ui components in their default state
- Focus on semantic HTML structure and accessibility
- Provide clean, functional components that I can style as needed

## Areas of Focus
Please prioritize these aspects when providing code suggestions:

- React Server Components by default - avoid "use client" unless truly needed for interactivity
- Server Actions for forms and data mutations over client-side API routes
- Component functionality and logic
- Proper TypeScript implementation  
- Accessibility and semantic HTML
- Component behavior and state management
- Integration with Next.js features (especially Server Actions and RSC)
- Performance considerations
- Clean component architecture

## What to Avoid
- Elaborate Tailwind styling unless specifically requested
- Color schemes, complex spacing, or visual flourishes
- Animations or transitions (I will add these myself)
- Over-engineered visual aspects
- Complex class combinations or inline styles

## Research and Documentation
- Please verify current best practices and look up the latest documentation when uncertain
- Check for recent updates to libraries and frameworks before suggesting implementations
- Reference official documentation for accurate syntax and patterns
- Stay current with the latest conventions and deprecation warnings

## Example Approach
Instead of: `<div className="bg-blue-500 p-6 rounded-lg shadow-xl border-2">`
Please provide: `<div className="p-4">` or simply `<div>`

I appreciate your focus on functionality and clean code structure. Thank you for helping me build applications efficiently while allowing me to handle the visual design aspects.