Commit Messages and Branching that Tell a Story
Use conventional commits, keep PRs focused, and write descriptions that explain motivation, not just code changes. Link issues, mention design trade‑offs, and reference screenshots. When someone skims history, they should feel guided through decisions, context, and outcomes without guessing intentions.