Self Documenting Code

This is a coding philosophy packaged as guidance for Claude. It pushes hard on making function names do the documentation work, splitting between "semantic" functions that are pure and reusable versus "pragmatic" ones that handle messy business logic. The models section is the strongest part, arguing that optional fields are technical debt and your types should make invalid states impossible. Brand types get a shoutout for preventing ID mixups. The advice is opinionated but practical, especially the warning about semantic functions slowly morphing into pragmatic ones because someone took a shortcut. Useful if you're trying to get Claude to write code that won't make you angry in six months.