Cursor rule

1---
2description: 
3globs: 
4alwaysApply: false
5---
6---
7description: If you are need to polish the code quality AFTER creating new tsx file. Read this rule
8globs: 
9alwaysApply: false
10---
11You have to follow these rules:
12## Do:
13 
141. Strictly follow requirements
152. Use functional programming techniques exclusively
163. Maintain immutability throughout
174. Use DRY principle across all files
185. Always have bun-first mindset
196. Always clean leftover unnecessary files
207. Highly reusability `react` FC functions in SINGLE tsx file
218. Use Ver and Hor based structure on tsx file
229. Within the nested ver hor, the last deepest child should use proper html semantic not div, ver hor
23 
24## Don't:
2510. Do not use `tailwind.config.js` it is deprecated in Tailwind CSS v4. v4 only needs `@import "tailwindcss";` in the CSS file.
2611. No DIV allowed, only use Ver Hor for directional component spreads
2712. Avoid OOP, classes, or inheritance
2813. Avoid traditional methods. use HOF
2914. Don't write // comments
3015. Don't use `any` or `unknown` types
3116. Don't use JSX elements like <div>, <Ver>, <Hor>, etc in the return statements, they should be extracted into separate functional FC components.
3217. No props drilling, use jotai
3318. use lucide react rather than writing svgs
3419. Do not create any new files other than these;
35    a. `src\components\page\*.page.tsx` : 
36    b. `src\components\ui\*.reuse.tsx` :
37    c. `src\types\common.type.ts` :
38    d. `src\types\props.type.ts` :
39    e. `src\state-management\hooks\*.hook.ts` : jotai useAtom
40    f. `src\state-management\hooks\*.state.ts` : jotai atom