juanmaguitar typescript-node-express-app .cursorrules file for TypeScript

You are an expert in Javascript, TypeScript and Node.js

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

Response Constraints

- Do not remove any existing code unless necessary
- Do not remove my comments or commented-out code unless necessary
- Do not change the formatting of my imports
- Do not change the formatting of my code unless important for new functionality

Code Style and Structure

- Write concise, technical TypeScript code with accurate examples
- Use functional and declarative programming patterns; avoid classes
- Prefer iteration and modularization over code duplication
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
- Structure files: exported component, subcomponents, helpers, static content, types
- Follow DRY (Don't Repeat Yourself) principle
- Implement early returns for better readability

Naming Conventions

- Use lowercase with dashes for directories (e.g., components/auth-wizard)
- Favor named exports for components
- 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

TypeScript Usage

- Use TypeScript for all code; prefer interfaces over types
- Avoid enums; use maps instead
- Use functional components with TypeScript interfaces
- Use TypeScript for all code
- Prefer interfaces over types
- Implement proper type safety and inference
- Use satisfies operator for type validation
- Use `node-ts` to directly execute typescript from terminal

Typescript config

```
{
	"compilerOptions": {
		"target": "es2018",
		"module": "commonjs",
		"moduleResolution": "node",
		"sourceMap": true,
		"outDir": "./dist",
		"rootDir": ".",
		"strict": true,
		"esModuleInterop": true,
		"skipLibCheck": true,
		"forceConsistentCasingInFileNames": true,
		"resolveJsonModule": true,
		"allowJs": true,
		"declaration": true,
		"lib": [ "ES2021" ]
	},
	"exclude": [ "node_modules" ]
}

```

Syntax and Formatting

- Use the "function" keyword for pure functions
- Use curly braces for all conditionals. Favor simplicity over cleverness

Code Quality

- Implement comprehensive error handling
- Write maintainable, self-documenting code
- Follow security best practices
- Ensure proper type coverage
- Use ESLint and Prettier

Testing Strategy

- Plan for unit and integration tests
- Implement proper test coverage
- Consider edge cases and error scenarios
- Validate accessibility compliance

Performance Optimization

- Look for ways to make things faster:
  - Use immutable data structures
  - Use efficient data fetching strategies
  - Optimize network requests
  - Use efficient data structures
  - Use efficient algorithms
  - Use efficient rendering strategies
  - Use efficient state management