These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
Use uv venv to create the virtual environment and run tests:
uv venv && source .venv/bin/activate
uv pip install -e ".[dev]"
pytest tests/When the user asks to stop tracking an item that is already tracked by Git, follow this exact procedure.
- Create a local backup copy first (same directory with
.baksuffix, or a timestamped copy). - Remove only from Git index with
git rm --cached <path>(never remove the local file). - Ensure an ignore rule exists in
.gitignorefor that path/pattern. - Verify the file still exists on disk.
- Verify Git reports it as ignored (
!!) and no unintended deletion is pending. - Only then commit.
Hard constraints:
- Never use
git rm <path>without--cachedfor this request type. - Never overwrite the local file as part of this operation.
- If there is any ambiguity, ask before running destructive or lossy steps.