AI SummaryCursor Rules that enforce a strict Bun & Biome development workflow, replacing npm/yarn with bun, Jest/Vitest with native bun:test, and eslint/prettier with Biome for faster, unified tooling.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "cursor-rules — Cursor Rules" prompt rules to my project. Repository: https://github.com/mynameistito/cursor-rules Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
My Cursor Rules and Commands.
Bun & Biome Workflow Standards
Trigger: Active globally. Apply these rules to all script execution, package management, and configuration tasks.
1. Package Management (Strict)
• Installer: ALWAYS use bun install or bun add. • Lockfile: bun.lockb is the single source of truth. Delete package-lock.json or yarn.lock immediately if found. • Manifest: Enforce specific version lock in package.json: `json "packageManager": "bun@1.3.x" `
2. Script & Command Execution
• Scripts: Replace npm run with bun run. • CLIs: ALWAYS use bunx (e.g., bunx drizzle-kit push). Never use npx, pnpm dlx, or yarn dlx. • Watch Mode Rules: • Web Frameworks (Next/Vite/Remix): Do NOT use bun --watch. Use standard bun run dev to preserve Hot Module Replacement (HMR). • Standalone Scripts/Servers: DO use bun --watch (e.g., bun --watch server.ts).
3. Testing (Native Bun)
• Runner: Use the built-in bun test runner. Do not install Jest or Vitest unless explicitly requested. • Syntax: Import strict native primitives: `typescript import { describe, test, expect } from "bun:test"; ` • Mocking: Use bun:test mocks (mock(), spyOn()).
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts