Hacker News Reader

Comment by podperson | Hacker News Reader

I wrote this library this weekend after realizing that Zod was really not designed for the use-cases I want JSON schemas for: 1) defining response formats for LLMs and 2) as a single source of truth for data structures.

View on HN

What led you to that conclusion?

And what makes this different? What makes it LLM-native?

It generates schemas that are strict by default while Zod requires you to set everything manually.

This is actually discussed in the linked article (READ ME file).

That's not true based on zod docs. https://zod.dev/api?id=objects

most of the claims you're making against zod is inaccurate. the readme feels like false claims by ai.

It seems to be true to me. And aside from the API stuff (because I am far from an expert user of Zod) all of this has been carefully verified.

Zod's validation errors are awful, the json schema it generates for LLM is ugly and and often confusing, the types structures Zod creates are often unintelligible in the and there's even no good way to pretty print a schema when you're debugging. Things are even worse if you're stuck with zod/v3

What's wrong with Zod validation errors?

None of this makes a lot of sense. Validation errors are largely irrelevant for LLMs and they can understand them just fine. The type structure looks good for LLMs. You can definitely pretty print a schema at runtime.

This all seems pretty uninformed.

1. Zoe’s documentation, such as it is 2. Code examples

Happy to see more tools in the data schema space.

Will you support Standard Schema (https://standardschema.dev)? How does this compare to typebox (https://github.com/sinclairzx81/typebox)?

Reply on news.ycombinator.com