Why case conventions matter operationally
Naming conventions look cosmetic until they break something. Environment variables must be CONSTANT_CASE; DNS labels and most Kubernetes object names must be lowercase kebab-case (RFC 1123: letters, digits, hyphens); Prometheus metrics use snake_case; JSON APIs mix camelCase and snake_case per ecosystem; and a filename with spaces will eventually escape someone's unquoted shell variable and ruin an afternoon. Converting a human-readable name into each of these forms correctly, including splitting exampleText at the case boundary, is exactly what this tool does, live as you type.
The slug row
The URL-slug conversion goes further than lowercasing: it strips diacritics via Unicode normalization (Café Über → cafe-uber), collapses every run of non-alphanumerics into a single hyphen, and trims leading and trailing hyphens. The result is safe for URLs, DNS labels, S3 keys, Docker image tags and Kubernetes names, the intersection of everyone's character rules.
Splitting rules
Words are detected at three boundaries: any non-alphanumeric character, a lower-to-upper transition (fooBar), and an acronym boundary (HTTPServer splits as HTTP + Server, not HTTPS + erver). That last rule is where naive converters usually fail. Numbers stick to the word they follow, so md5sum stays one token rather than becoming md-5-sum.