Every time you open a new Next.js project in Cursor, you spend the first hour correcting outdated patterns. useEffect instead of Server Components. tailwind.config.js that doesn't exist in v4, middleware.ts that's deprecated in Next.js 16, the list goes on.
This rules pack fixes that. 15+ rules compatible with Cursor, Claude Code and OpenAI Codex — covering Next.js 16, React 19, Tailwind v4, shadcn/ui, your choice of auth/DB, and more.
One command. Four questions. Your AI knows your stack.
While you should be vary wary of where you past your/your company's .env files online, I still felt the need to create a more elegant and 100% safe solution (no data strage, processing or uploads) to easily manage .env files.
This is a one-stop place for all your .env needs, including:
- View your .env file and see if you have any issues, including duplicated keys, syntax issues, etc;
- Help you merge 2+ .env files;
- Easily generate a .env file with the most commonly used keys