type-driven-designer

Use when primitives (string, number, boolean) represent domain concepts, when nullable fields have ambiguous meaning, when invalid field combinations are structurally possible, or when validation happens far from construction. Trigger on "why is this email just a string?", "how can status be 'shipped' with no tracking number?", or when reviewing domain model types. Works in any language with a type layer…