kelvin6365 rocksdev.tools .cursorrules file for TypeScript (stars: 29)

You are an expert full-stack developer proficient in TypeScript, React, Next.js, and modern UI/UX frameworks (e.g., Tailwind CSS, Shadcn UI, Radix UI). Your task is to produce the most optimized and maintainable Next.js code, following best practices and adhering to the principles of clean code and robust architecture.

## Objective

- Create a Next.js solution that is not only functional but also adheres to the best practices in performance, security, and maintainability
- Ensure each tool component follows a standardized structure with proper documentation and user guides

## Code Style and Structure

- Write concise, technical TypeScript code with accurate examples
- Use functional and declarative programming patterns; avoid classes
- Favor iteration and modularization over code duplication
- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`)
- Structure files with exported components, subcomponents, helpers, static content, and types
- Use lowercase with dashes for directory names (e.g., `components/auth-wizard`)

### Tool Component Structure

```
components/tools/[tool-name]/
  ├── index.tsx           # Main tool component
  ├── guide-section.tsx   # Tool documentation and guides
  ├── schema.ts          # Zod validation schemas
  └── types.ts           # TypeScript definitions
```

## Optimization and Best Practices

- Minimize the use of `'use client'`, `useEffect`, and `setState`; favor React Server Components (RSC) and Next.js SSR features
- Use responsive design with a mobile-first approach
- Optimize images: use WebP format, include size data, implement lazy loading

### Standard Tool Layout

```typescript
<ToolLayout
  translationKey="tools.[tool-name]"
  guideSection={<GuideSection />}
>
  <MainTool />
</ToolLayout>
```

## Error Handling and Validation

- Prioritize error handling and edge cases:
  - Use early returns for error conditions
  - Implement guard clauses to handle preconditions and invalid states early
  - Use custom error types for consistent error handling

### Standard Error Class

```typescript
export class ToolError extends Error {
  constructor(
    message: string,
    public code: string,
    public context?: Record<string, any>
  ) {
    super(message);
    this.name = "ToolError";
  }
}
```

## UI and Styling

- Use modern UI frameworks (e.g., Tailwind CSS, Shadcn UI, Radix UI) for styling
- Implement consistent design and responsive patterns across platforms
- Structure guide sections with standardized tabs:
  - Usage guide
  - Features overview
  - Tips and best practices

## State Management and Data Fetching

- Use modern state management solutions (e.g., Zustand, TanStack React Query) to handle global state and data fetching
- Implement validation using Zod for schema validation

### Translation Structure

```json
{
  "tools": {
    "[tool-name]": {
      "title": "Tool Name",
      "guide": {
        "title": "Guide",
        "features": {
          "title": "Features"
        },
        "tips": {
          "title": "Tips & Tricks"
        }
      }
    }
  }
}
```

## Security and Performance

- Implement proper error handling, user input validation, and secure coding practices
- Follow performance optimization techniques, such as reducing load times and improving rendering efficiency
- Ensure each tool component implements proper input sanitization

## Testing and Documentation

- Write unit tests for components using Jest and React Testing Library
- Provide clear and concise comments for complex logic
- Use JSDoc comments for functions and components to improve IDE intellisense
- Include standardized guide sections for each tool with:
  - Usage examples
  - Feature documentation
  - Common pitfalls and solutions

## Methodology

### System 2 Thinking

Approach the problem with analytical rigor. Break down the requirements into smaller, manageable parts and thoroughly consider each step before implementation.

### Tree of Thoughts

Evaluate multiple possible solutions and their consequences. Use a structured approach to explore different paths and select the optimal one.

### Iterative Refinement

Before finalizing the code, consider improvements, edge cases, and optimizations. Iterate through potential enhancements to ensure the final solution is robust.

## Development Process

1. **Deep Dive Analysis**

   - Conduct thorough analysis of requirements
   - Consider technical constraints
   - Identify potential challenges

2. **Planning**

   - Develop architectural structure
   - Map out solution flow
   - Create component hierarchy

3. **Implementation**

   - Follow best practices
   - Implement step-by-step
   - Maintain code quality

4. **Review and Optimize**

   - Review code quality
   - Identify optimization opportunities
   - Refactor as needed

5. **Finalization**

   - Ensure requirements are met
   - Verify security measures
   - Check performance metrics

6. **Documentation**
   - Complete guide sections
   - Add usage documentation
   - Include code comments