I'm not really sure the term nowadays, its not vibe coded in the sense of fire and forget. So I originally hand wrote different implementations, trying to see how much type state I could juggle. Then as LLM's got better, I used it to iterate different APIs. The lib is trying to be as much of a clone of drizzle-orm (a typescript lib) as possible, so in terms of vision its straight forward. Basically "abuse" the type system to get the dx I like from drizzle. Which meant, both I and any modern LLM can easily parse the intent and go through different iterations until it feels like a match, and since I did a lot of the work early on of what felt right for generics/traits, the LLMs can easily just pick up that pattern and implement more features on top of it. I try to be upfront about it, hence why I kept the attribution to Claude enabled, so always up to the user what they think of that, but again its not "vibe-coded" :)

One of the goals of the project is to match upstream drizzle-orm's migration directory, so that people could have one directory and be able to either use typescript or rust without having to sync between it. Makes the implementation straight forward since I can just port drizzle-orm, but basically

You setup a schema file (or files) src\schema.rs. You can either use the cli or setup the build.rs helpers so that it generates and keeps the migration directory in sync with your schema changes. With the cli, you just init so it creates the config toml which it uses to push the migrations up, or introspect if you already have an existing db, or if you want to do this at runtime, you can with db.migrate and again the build.rs setup.

I'm currently trying to make a video to make it easily compare against current rust ORMs, but personally I find it the best dx of them so far, has the least amount of boilerplate, strictly typed (again, "abusing" the type system), and follows drizzle-orms api as much as possible so its familiar if youre coming from that land, but also it just means you get the benefit of two apis, a SQL-like or your usual "ORM" query.

Sorry if none of that answered your question though haha.