The BSL-1.1 license choice is interesting too — shows you're thinking about sustainability and intent, not just shipping fast. That kind of explicit decision-making is actually what separates vibe coding projects that survive from ones that collapse: when the human behind the project is thinking about architecture, maintainability, and accountability.
Somewhat related: the Agile Vibe Coding Manifesto (https://agilevibecoding.org) is trying to formalize exactly these principles — that customer value and human accountability still drive everything even when AI is writing most of the code. Your project is a good example of vibe coding done with intention.
Good luck with Skales — the accessibility angle (no Docker, no CLI) is genuinely underserved.