Comment by jurf

That's a lot of context for not much content. I ussually start with something like:

- Prefer documentation as code

- Comment why, not what

- Document public APIs

- Readability is paramount

That usually gets me 80% there; rest is covered by the linter.

I'm mostly just missing it explaining previous state too much, especially when making edits to plans, but I have not found good wording for that yet.