Cursor rule

1---
2description: Follow these rules for all requests.
3globs: 
4alwaysApply: false
5---
6# Project Instructions
7# Project Instructions
8 
9Use specification and guidelines as you build the app.
10 
11Write the complete code for every step. Do not get lazy.
12 
13Your goal is to completely finish whatever I ask for.
14 
15You will see <ai_context> tags in the code. These are context tags that you should use to help you understand the codebase.
16 
17## Overview
18 
19This is a web app template.
20 
21## Tech Stack
22 
23- Frontend: Next.js, Tailwind, Shadcn, Framer Motion
24- Backend: Postgres, Supabase, Drizzle ORM, Server Actions
25- Auth: Clerk
26- Payments: Stripe
27- Analytics: PostHog
28- Deployment: Vercel
29 
30## Project Structure
31 
32- `actions` - Server actions
33  - `db` - Database related actions
34  - Other actions
35- `app` - Next.js app router
36  - `api` - API routes
37  - `route` - An example route
38    - `_components` - One-off components for the route
39    - `layout.tsx` - Layout for the route
40    - `page.tsx` - Page for the route
41- `components` - Shared components
42  - `ui` - UI components
43  - `utilities` - Utility components
44- `db` - Database
45  - `schema` - Database schemas
46- `lib` - Library code
47  - `hooks` - Custom hooks
48  - `services` - Business logic services
49- `prompts` - Prompt files
50- `public` - Static assets
51- `types` - Type definitions
52 
53## Rules
54 
55Follow these rules when building the app.
56 
57### General Rules
58 
59- Use `@` to import anything from the app unless otherwise specified
60- Use kebab case for all files and folders unless otherwise specified
61- Don't update shadcn components unless otherwise specified
62 
63#### Env Rules
64 
65- If you update environment variables, update the `.env.example` file
66- All environment variables should go in `.env.local`
67- Do not expose environment variables to the frontend
68- Use `NEXT_PUBLIC_` prefix for environment variables that need to be accessed from the frontend
69- Always access environment variables via the centralized config module (`serverConfig` and `publicEnv` from `@/lib/config`). Do not use `process.env` directly in application code.
70 
71#### Type Rules
72 
73Follow these rules when working with types.
74 
75- When importing types, use `@/types`
76- Name files like `example-types.ts`
77- All types should go in `types`
78- Make sure to export the types in `types/index.ts`
79- Prefer interfaces over type aliases
80- If referring to db types, use `@/db/schema` such as `SelectTodo` from `todos-schema.ts`
81 
82An example of a type:
83 
84`types/actions-types.ts`
85 
86```ts
87export type ActionState<T> =
88  | { isSuccess: true; message: string; data: T }
89  | { isSuccess: false; message: string; data?: never }
90```
91 
92And exporting it:
93 
94`types/index.ts`
95 
96```ts
97export * from "./actions-types"
98```
99 
100- Always access environment variables via the centralized config module (`serverConfig` and `publicEnv` from `@/lib/config`). Do not use `process.env` directly in application code.
101 
102