Default to using Bun instead of Node.js.
# FlowSales Project Rules Default to using Bun instead of Node.js. ## Commands - Use `bun <file>` instead of `node <file>` or `ts-node <file>` - Use `bun test` instead of `jest` or `vitest` - Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild` - Use `bun install` instead of `npm install` or `yarn install` or `pnpm install` - Use `bun run <script>` instead of `npm run <script>` or `yarn run <script>` or `pnpm run <script>` - Use `bunx <package> <command>` instead of `npx <package> <command>` - Bun automatically loads .env, so don't use dotenv. ## Language & Communication - 全てのアーティファクト(Implementation Plan, Walkthrough, 等)およびテクニカルドキュメントは、日本語で作成してください。 - ファイルやディレクトリ、関数名、クラス名などを参照する際は、バッククォート(` `)で囲み、可能な限りリンク([file.ts](file:///path/to/file.ts))を併用してください。 ## Preferred APIs - `Bun.serve()` supports WebSockets, HTTPS, and routes. Don't use `express`. - `bun:sqlite` for SQLite. Don't use `better-sqlite3`. - `Bun.redis` for Redis. Don't use `ioredis`. - `Bun.sql` for Postgres. Don't use `pg` or `postgres.js`. - `WebSocket` is built-in. Don't use `ws`. - Prefer `Bun.file` over `node:fs`'s readFile/writeFile - Bun.$`ls` instead of execa. ## Frontend Use HTML imports with `Bun.serve()`. Don't use `vite`. HTML imports fully support React, CSS, Tailwind. Bun's bundler will transpile & bundle automatically.
Comprehensive .cursorrules file for Next.js 15 App Router projects with TypeScript, enforcing server components by default, proper use of "use client" directive, and App Router conventions.
Cursor rules for Python FastAPI projects enforcing async patterns, Pydantic v2 models, dependency injection, and proper error handling.
Rules for consistent React component development with TypeScript interfaces, proper hook patterns, and component composition.
Rules optimizing Cursor Agent mode behavior including multi-file editing context, session management, and autonomous task completion patterns.
Cursor rules for projects using Tailwind CSS with shadcn/ui component library, enforcing consistent utility class usage and component patterns.
Rules for Go backend services enforcing idiomatic Go patterns, proper error handling, and clean architecture conventions.