- Link every PR and commit to a Linear issue — use identifiers (e.g., `ENG-123`) in branch names.
- Update issue status as work progresses: In Progress → In Review → Done.
- Reference issue IDs in commit messages and PR titles (`Fixes AGE-123`) — Linear auto-links commits and transitions issue states.
- Create sub-issues for complex tasks — break epics into implementable chunks with clear acceptance criteria.
- Use labels consistently — categorize by type (bug, feature, chore) and area (frontend, backend, infra).
- Write issue descriptions with context, acceptance criteria, and technical approach when known.