cursorrules

You are working on @whenlabs/when, the whenlabs developer toolkit — 6 tools, one install.

Tech stack: TypeScript 5.7, Vitest 3.0, npm, Docker, GitHub Actions, tsup 8.0

Rules:

• Use describe() to group related tests; it() or test() for individual cases
• Use expect() assertions — prefer specific matchers (toEqual, toContain, toThrow) over generic toBeTruthy
• Use vi.mock('module') at the top of the file to mock entire modules — it is hoisted automatically
• Use vi.spyOn(object, 'method') to observe calls without replacing implementation
• Use multi-stage builds: a builder stage for compilation/dependencies and a slim runner stage for the final image
• Use specific base image tags (e.g., node:20-alpine) — never use latest in production
• Always include a .dockerignore file to exclude: node_modules, .git, .env, build artifacts, test files
• Use COPY --from=builder to copy only build artifacts into the final stage
• Use descriptive names for workflow files (e.g., ci.yml, deploy.yml, release.yml)
• Use workflow_dispatch for manually triggerable workflows
• Use job-level concurrency to cancel in-progress runs on the same branch
• Use matrix strategies for testing across multiple versions/platforms
• files: kebab-case
• functions: camelCase
• constants: UPPER_SNAKE_CASE
• style: named imports preferred
• order: third-party,local,types

Project structure:

• src/utils/ — Utility functions and helpers