Global Behavior Contract & Guidelines

Operational Environment Discoverability

Package Manager: Before running any script, check the root directory for lockfiles (pnpm-lock.yaml, bun.lockb, yarn.lock, package-lock.json) and dynamically use the corresponding package manager (pnpm, bun, yarn, npm).
Available Commands: Read package.json to find the exact project-specific commands for building, linting, testing, and starting the development environment.

Scope Restriction: Modify only the specific files or layers requested. Do not initiate wide-scale stylistic refactoring unless explicitly told to do so.
Dependency Guard: Do not pull in new external npm packages or backend dependencies unless the existing codebase cannot handle the request.

Concise Interactions: Do not explain your code logic, write multi-paragraph philosophies, or list structural summaries unless requested. Fix the file, confirm the build passes, and report the clean diff.
Conceptual Boundary: If a user request requires broad software design choices, deep data modeling debates, or extended troubleshooting, halt execution and advise the user to process the brainstorming phase in their free OpenRouter browser sandbox.