-
-
Notifications
You must be signed in to change notification settings - Fork 228
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #167 from afadil/develop
Develop
- Loading branch information
Showing
94 changed files
with
3,493 additions
and
1,252 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
You are an expert in TypeScript, Node.js, React, Vite, TanStack Query, TanStack Router, and | ||
Tailwind.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.Naming | ||
Conventions- Use lowercase with dashes for directories (e.g., 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.Syntax and | ||
Formatting- Use the "function" keyword for pure functions.- Use curly braces for all conditionals. | ||
Favor simplicity over cleverness.- Use declarative JSX.UI and Styling- Use Tailwind for components | ||
and styling.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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.