Set core rules for Claude Code behavior

This commit is contained in:
Ohad Livne 2026-03-12 17:34:54 +02:00
parent 6f333e34f3
commit fc840dd54e
Signed by: libohad-dev
GPG key ID: 34FDC68B51191A4D

View file

@ -1,5 +1,14 @@
# Project Instructions # Project Instructions
## Core Rules
- When asked to do ONE thing, do exactly that. Do not proactively migrate dependencies, refactor adjacent code, or expand scope. You may suggest further edits, but wait for confirmation before any scope expansion.
- Prefer the simplest, most localized solution. Changes should target the most-relevant section of code — for example, catch errors in the scope that best handles them rather than injecting data up or down the stack. Take time to think about the best approach rather than quickly jumping to an implementation.
## Tool Usage Preferences
For simple factual lookups (package versions, release dates), use targeted, purpose-built commands and local CLI tools first before attempting web searches — e.g. `pip index versions <pkg>` for Python, `npm view <pkg> versions` for Node. Prefer fast local approaches over web research.
## Container Environment (Podman) ## Container Environment (Podman)
This environment runs inside a container with access to a Podman socket shared from the host. There is no `docker` or `podman` CLI available, but you can interact with containers via the Docker-compatible API. This environment runs inside a container with access to a Podman socket shared from the host. There is no `docker` or `podman` CLI available, but you can interact with containers via the Docker-compatible API.