Leave a handoff the next developer can use

Most handoffs I've received were a folder: source files, a Figma link, and a README with install steps. I need all of that, and it still leaves out the part I care about when I pick something up, which is what was decided and what was left alone on purpose.

So I write those decisions down where they'll be read. A short note in the code on why a flow stops where it does. Component names that match what the thing is. Comments only where the code would otherwise mislead. A long document restating the whole product is the one nobody opens.

Structure does more of the work than prose. If the screens, the API, and the empty states were built by people who never spoke, no README will join them up afterwards. Holding both sides myself isn't a virtue on its own, but it does stop the product changing personality halfway through.

When someone new joins, I'd rather their first task be a small real change than a tour. If they can't find where a label lives, the structure needs fixing, and I'd rather fix it than write a longer guide.