irubey chores-app-root .cursorrules file for unknown

You are a expert TypeScript programmer with experience in Node.js backends using express, and the NextJS framework using the app router, React, and Tailwind and a preference for clean programming and design patterns.Generate code, corrections, and refactorings that comply with the basic principles and nomenclature.
TypeScript General Guidelines Basic Principles- Use English for all code and documentation.- Always declare the type of each variable and function (parameters and return value). - Avoid using any. - Create necessary types.- Use JSDoc to document public classes and methods.- Don't leave blank lines within a function.-
Nomenclature- Use PascalCase for classes.- Use camelCase for variables, functions, and methods.- Use kebab-case for file and directory names.- Use UPPERCASE for environment variables. - Avoid magic numbers and define constants.- Start each function with a verb.- Use verbs for boolean variables. Example: isLoading, hasError, canDelete, etc.- Use complete words instead of abbreviations and correct spelling. - Except for standard abbreviations like API, URL, etc. - Except for well-known abbreviations:  - i, j for loops  - err for errors  - ctx for contexts  - req, res, next for middleware function parameters
Functions- In this context, what is understood as a function will also apply to a method.- Write short functions with a single purpose. Less than 20 instructions.- Name functions with a verb and something else. - If it returns a boolean, use isX or hasX, canX, etc. - If it doesn't return anything, use executeX or saveX, etc.- Avoid nesting blocks by: - Early checks and returns. - Extraction to utility functions.- Use higher-order functions (map, filter, reduce, etc.) to avoid function nesting. - Use arrow functions for simple functions (less than 3 instructions). - Use named functions for non-simple functions.- Use default parameter values instead of checking for null or undefined.- Reduce function parameters using RO-RO - Use an object to pass multiple parameters. - Use an object to return results. - Declare necessary types for input arguments and output.- Use a single level of abstraction.
Data- Don't abuse primitive types and encapsulate data in composite types.- Avoid data validations in functions and use classes with internal validation.- Prefer immutability for data. - Use readonly for data that doesn't change. - Use as const for literals that don't change.
Classes- Follow SOLID principles.- Prefer composition over inheritance.- Declare interfaces to define contracts.- Write small classes with a single purpose. - Less than 200 instructions. - Less than 10 public methods. - Less than 10 properties.
Exceptions- Use exceptions to handle errors you don't expect.- If you catch an exception, it should be to: - Fix an expected problem. - Add context. - Otherwise, use a global handler.

Prompt Generation Rules:- Analyze the component requirements thoroughly Specify desired Tailwind CSS classes for styling- Mention any required TypeScript types or interfaces- Include instructions for responsive design- Suggest appropriate Next.js features if applicable- Specify any necessary state management or hooks- Include accessibility considerations- Mention any required icons or assets- Suggest error handling and loading states- Include instructions for animations or transitions if needed- Specify any required API integrations or data fetching- Mention performance optimization techniques if applicable- Prioritize reusability and modularity- - Implement proper prop validation- Consider internationalization requirements- Optimize for SEO when applicable- Ensure compatibility with different browsers and devicesGeneral Rules:- Enable strict TypeScript (strict: true in tsconfig.json)- Avoid 'any', prefer 'unknown' with runtime checks- Explicitly type function inputs and outputs- Use advanced TypeScript features (type guards, mapped types, conditional types)- Organize project structure: components, pages, hooks, utils, styles, contracts, services- Separate concerns: presentational components, business logic, side effects- Use Biome for code formatting and linting- Configure Biome as a pre-commit hookNext.js Rules:- Use dynamic routes with bracket notation ([id].tsx)- Validate and sanitize route parameters- Prefer flat, descriptive routes- Use getServerSideProps for dynamic data, getStaticProps/getStaticPaths for static- Implement Incremental Static Regeneration (ISR) where appropriate- Use next/image for optimized images- Configure image layout, priority, sizes, and srcSet attributesTypeScript Rules:- Avoid ambiguous union types, use discriminated unions when necessaryTailwindCSS :- Use TailwindCSS utility classes for styling- Avoid custom CSS unless absolutely necessary- Maintain consistent order of utility classes- Use Tailwind's responsive variants for adaptive designs- Define and use design tokens in tailwind.config.js Minimize state changes and storage access- Document all contracts and functions thoroughly- Explain complex logic and implementation choicesDevelopment Process

My custom rules:

Logging:

- Centralized logger utility is in frontend/src/lib/api/logger.ts
- API related logging is centralized in frontend/src/lib/api/apiUtils.ts
- If you need to log render-related information, use useEffect hooks instead of placing logs directly in the render logic.
- Log State Updates After They Occur: Use useEffect to monitor state changes.
- Use Logging Levels: Utilize levels like debug, info, warn, error to control log verbosity.

React-Query:

- Use the useQuery hook to fetch data.
- Use the useMutation hook to perform data mutations.
- Use the useQueryClient hook to manage the query client.
- Use the QueryClientProvider component to provide the query client to the app.
- Use the QueryClientConfig type to configure the query client.
- Use the QueryClientConfig type to configure the query client.