# engineer-CLAUDE.md

Personal workflow preferences. Loaded after org-CLAUDE.md and repo-CLAUDE.md. Both win where they conflict.

**Example file** showing what belongs at the engineer level. Adapt the preferences to your own workflow. The structure matters more than the specifics.

**Tradeoff:** This file exists for personal velocity. It cannot make decisions that affect other engineers, shared code, or team workflow. Anything that does belongs in repo-CLAUDE.md.

## 1. Communication Preferences

**Use bullets in PR descriptions. I review faster from bullets.**

- When summarizing what changed, use a bulleted list.
- When suggesting variable names, prefer descriptive over short. `user_subscription_status`, not `uss`.

## 2. Local Workflow

**`make test-fast` is enough for the local loop. CI runs the full suite.**

- Do not run the full test suite locally during development unless I ask.
- When running interactively, show me the proposed refactor diff and wait for my confirmation. In headless mode, proceed and document the change in the PR description.

## 3. What This File Cannot Do

**If a rule here would affect shared code or the team, the rule belongs elsewhere.**

This file does not override:
- Any security rule in org-CLAUDE.md.
- Any stack choice in repo-CLAUDE.md, including pytest, `internal/http`, or `data/repositories/`.
- Any review gate or escalation path.

If I try to add a rule here that affects code other engineers will touch, stop. Tell me the rule belongs in repo-CLAUDE.md instead, and that I should raise it with the repo lead.