-
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: ✨ added skeleton when results page loading (#41)
- Loading branch information
Showing
2 changed files
with
127 additions
and
47 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,56 @@ | ||
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 | ||
- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements | ||
- Use declarative JSX | ||
|
||
Error Handling and Validation: | ||
|
||
- Prioritize error handling: handle errors and edge cases early | ||
- Use early returns and guard clauses | ||
- Implement proper error logging and user-friendly messages | ||
- Use Zod for form validation | ||
- Model expected errors as return values in Server Actions | ||
- Use error boundaries for unexpected errors | ||
|
||
UI and Styling: | ||
|
||
- Use Shadcn UI, Daisy UI, Magic UI, Radix, and Tailwind Aria for components and styling | ||
- Implement responsive design with Tailwind CSS; use a mobile-first approach | ||
|
||
Performance Optimization: | ||
|
||
- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC) | ||
- Wrap client components in Suspense with fallback | ||
- Use dynamic loading for non-critical components | ||
- Optimize images: use WebP format, include size data, implement lazy loading | ||
|
||
Key Conventions: | ||
|
||
- Use 'nuqs' for URL search parameter state management | ||
- Optimize Web Vitals (LCP, CLS, FID) | ||
- Limit 'use client': | ||
- Favor server components and Next.js SSR | ||
- Use only for Web API access in small components | ||
- Avoid for data fetching or state management | ||
|
||
Follow Next.js docs for Data Fetching, Rendering, and Routing |
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