-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.cursorrules
More file actions
45 lines (39 loc) · 1.55 KB
/
.cursorrules
File metadata and controls
45 lines (39 loc) · 1.55 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# Project: Next.js Boilerplate Application
## General
- This is a Next.js TypeScript application with App Router.
- Use React for components development, prefer to use functional components.
- Use Tailwind CSS for styling.
- Use Shadcn UI components.
- Use sonner for toast notifications.
- Use React Context for state management.
- Component names are in CamelCase.
- Use next-auth for authentication.
- Use next-intl for internationalization.
- Use Stripe for payment.
## File Structure
- src/app/: Next.js App Router pages and API routes
- [locale]/: Locale-specific pages
- api/: API routes (e.g. checkout)
- theme.css: Theme styles
- src/components/: React components
- blocks/: Layout blocks (header, footer, etc.), commonly used in Landing Page
- ui/: Reusable UI components
- src/contexts/: React contexts (e.g. app context)
- src/i18n/: Internationalization
- pages/landing/: Page-specific translations for Landing Page
- messages/: Global messages
- src/types/: TypeScript type definitions
- blocks/: Types for layout blocks
- pages/: Types for pages
- src/models/: Data models and data operations.
- src/services/: Business logics.
- src/lib/: Custom libraries and functions
- public/: Static assets
- .env.development: Development environment variables
## Coding Conventions
- Use TypeScript for type safety
- Follow React best practices and hooks
- Implement responsive design with Tailwind CSS and Shadcn UI
- Maintain consistent internationalization structure
- Keep components modular and reusable
- Use proper type definitions for components and data