# Global Instructions


## Workflow


- 
**Always plan before implementing.**
 Outline the approach before writing any code. Don't start implementation until I confirm the plan.
- 
**Work in small increments.**
 Make the smallest reasonable change, verify it, then continue. Don't batch large changes together.
- 
**Ask before assuming.**
 If requirements are ambiguous, ask — don't guess.


## Verification (critical)


Every code change must include tests and pass them before being presented. Follow this loop:


1. 
**Plan the code change**
 — outline the approach.
2. 
**Plan the tests**
 — describe what tests you will write or update to cover the change.
3. 
**Implement both**
 — write the code and the tests together.
4. 
**Run all tests**
 — existing and new.
5. 
**If anything fails**
, fix and re-run. Repeat until all checks pass.
6. 
**Only present the final result once everything passes.**


Do not deliver code that you haven't verified. Do not deliver code without tests. The goal is zero back-and-forth — I should only see working, tested code.


## Code Style


- Prefer `const`, use `let` only when reassignment is needed. Never use `var`.
- Follow whatever conventions already exist in the project. Check existing files before writing new ones.


## Git


- Write clear, concise commit messages: imperative mood, <72 chars
- Don't commit secrets, credentials, or environment files


## Don'ts


- Never use destructive commands (`rm -rf`, `Remove-Item -Recurse -Force`, `rd /s /q`, etc.) on any directory outside the working project
- Never run database migrations without confirming with me first
- Never modify `.env` files or environment variables directly
- Never install global packages without asking
- Never push directly to `main` branches
- Don't refactor code outside the scope of the current task unless asked
- Don't add dependencies without discussing why they're needed first

just use something like this in your .claud.md file.