// Update workspace packages while respecting the repo's pinned package list in .ncurc.cjs. Use when the user asks to update dependencies or refresh package versions.
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
Cursor Cloud VM setup and service startup instructions for local development
Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.
Commit changes and open a pull request with safe metadata
Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for product use; and find repeated instructions between the main prompt and tool descriptions.
Add a new changelog entry to docs/changelog-entries/
| name | update-packages |
| description | Update workspace packages while respecting the repo's pinned package list in .ncurc.cjs. Use when the user asks to update dependencies or refresh package versions. |
Use this workflow when updating dependencies in this repo.
.ncurc.cjs. Do not upgrade packages listed there..nvmrc, engines.node, @types/node, Dockerfiles, and CI together.pnpm dlx npm-check-updates -u -ws
pnpm install
pnpm test
pnpm lint
npm-check-updates reads .ncurc.cjs, so the reject list is applied during the manifest update.pnpm install may also bump the root packageManager field and regenerate pnpm-lock.yaml.pnpm dev or pnpm build unless the user explicitly asks.@hookform/resolvers in the .ncurc.cjs reject list and pinned to 4.1.0 while apps/web remains on zod@3.25.76. The 5.x resolver line imports zod/v4/core, which has caused local Next.js/Turbopack resolution failures even though the app code still uses Zod 3.