Cursor Rules - Custom AI Instructions

# React + TypeScript Project Rules

## Code Style
- Use TypeScript for all files (.ts, .tsx)
- Use functional components with hooks
- Use arrow functions: const MyComponent = () => {}
- Use named exports, not default exports
- Use 2 spaces for indentation
- Use single quotes for strings
- Add semicolons at end of statements

## Component Guidelines
- Use TypeScript interfaces for props
- Name components with PascalCase
- Keep components small and focused (< 200 lines)
- Extract complex logic into custom hooks
- Use Tailwind CSS for styling (no CSS modules)

## State Management
- Use React hooks (useState, useEffect, useContext)
- For global state, use Zustand
- Never use Redux

## File Organization
- Components in src/components/
- Hooks in src/hooks/
- Types in src/types/
- Utils in src/utils/

## Documentation
- Add JSDoc comments for complex functions
- Include prop descriptions in TypeScript interfaces
- Add README.md for each major feature

## Testing
- Write tests using Vitest
- Use React Testing Library for component tests
- Aim for 80% coverage

## Avoid
- Class components
- PropTypes (use TypeScript)
- Inline styles (use Tailwind)
- Any type (be specific)
- console.log in production code

# Next.js 15 App Router Rules

## Framework Conventions
- Use Next.js 15 App Router (not Pages Router)
- Server Components by default
- Add "use client" only when necessary
- Use Server Actions for mutations
- Use route handlers for API endpoints

## File Structure
- Pages in src/app/
- Components in src/components/
- Server actions in src/app/actions/
- API routes in src/app/api/

## Data Fetching
- Use async Server Components for data fetching
- Use fetch with Next.js caching
- Use Server Actions for form submissions
- Never use useEffect for data fetching

## Styling
- Use Tailwind CSS
- Use CSS variables for theming
- Mobile-first responsive design

## Performance
- Use next/image for images
- Use next/font for fonts
- Implement loading.tsx and error.tsx
- Use Suspense for streaming

## SEO
- Add metadata to every page
- Use generateMetadata for dynamic pages
- Include OpenGraph and Twitter cards

## TypeScript
- Strict mode enabled
- No any types
- Define return types for functions

# Python FastAPI Backend Rules

## Code Style
- Follow PEP 8 style guide
- Use type hints for all functions
- Use async/await for I/O operations
- Use 4 spaces for indentation
- Maximum line length: 88 characters (Black formatter)

## Framework
- Use FastAPI for API endpoints
- Use Pydantic for data validation
- Use SQLAlchemy for database ORM
- Use Alembic for migrations

## Project Structure
- API routes in app/routes/
- Models in app/models/
- Schemas in app/schemas/
- Database logic in app/db/
- Business logic in app/services/

## Error Handling
- Use HTTPException for API errors
- Include descriptive error messages
- Log errors with proper severity levels
- Never expose internal errors to clients

## Security
- Use environment variables for secrets
- Validate all user input with Pydantic
- Use OAuth2 with JWT tokens
- Hash passwords with bcrypt

## Testing
- Use pytest for testing
- Mock external dependencies
- Aim for 90% code coverage
- Include integration tests for API endpoints

## Documentation
- Add docstrings to all functions (Google style)
- Keep OpenAPI/Swagger docs up to date
- Include example requests/responses

# [Project Name] Cursor Rules

## Overview
[Brief description of project and tech stack]

## Code Style
- Language: [e.g., TypeScript, Python]
- Formatter: [e.g., Prettier, Black]
- Linter: [e.g., ESLint, Pylint]
- Indentation: [spaces/tabs, size]
- Quotes: [single/double]
- [Other style preferences]

## Framework & Libraries
- Primary framework: [e.g., Next.js, FastAPI]
- Preferred libraries:
  - [Library 1]: [Use case]
  - [Library 2]: [Use case]
- Avoid:
  - [Library to avoid]: [Reason]

## File Organization
- [Directory]: [Purpose]
- [Directory]: [Purpose]
- Naming conventions: [Details]

## Component/Function Guidelines
- [Specific patterns to follow]
- [Size limits]
- [Documentation requirements]

## State Management
- [Approach to use]
- [When to use what]

## Error Handling
- [How to handle errors]
- [Logging approach]

## Testing
- Framework: [e.g., Jest, pytest]
- Coverage target: [e.g., 80%]
- [Testing conventions]

## Security
- [Security requirements]
- [Authentication approach]

## Performance
- [Performance guidelines]
- [Optimization strategies]

## Documentation
- [Documentation requirements]
- [Comment style]

## Avoid
- [Anti-patterns]
- [Deprecated features]
- [Known issues]