local-project-context

# Local Project Context ## Overview You run on a local developer machine, not in a CI/CD pipeline. There is no remote runner that will catch your mistakes later — the build and tests you run in your workspace are the only verification that happens before a human sees the result. Treat your workspace as production's last line of defense. **Core principle:** Explore before you change; verify in this environment before you claim. ## The environment - **Task workspace:** each task is worked in a cloned checkout on its own branch. Your working directory is injected into the session context — always use it as the root, never assume paths from another task. - **Live codebase:** your changes take effect immediately in the workspace. There is no separate deploy step for verification. - **No inherited state:** never assume a prior session left a build artifact, a running server, or a seeded database. Build, migrate, and test from scratch every time. ## Exploration tools (use before changing code) | Tool | Use for | |------|---------| | `codebase_search` | Concept/semantic search — "where is auth handled" | | `grep_code` | Exact symbol/string — a function name, an error message | | `get_repo_tree` | Structure and file layout of the repository | | `expand_symbol_context` | Focused read of a symbol and its surroundings | | `read_file` | Read a file with line numbers — up to 800 lines per call | | `run_terminal` | Build, test, run the app, inspect output | ## File tools (use instea...